Recherche avancée

Sur d’autres sites (11760)

• How Piwik uses Travis CI to deliver a reliable analytics platform to the community

  26 mai 2014, par Matthieu Aubry — Development, Meta

  In this post, we will explain how the Piwik project uses continuous integration to deliver a quality software platform to dozens of thousands of users worldwide. Read this post if you are interested in Piwik project, Quality Assurance or Automated testing.

  Why do we care about tests ?

  Continuous Integration brings us agility and peace of mind. From the very beginning of the Piwik project, it was clear to us that writing and maintaining automated tests was a necessity, in order to create a successful open source software platform.

  Over the years we have invested a lot of time into writing and maintaining our tests suites. This work has paid off in so many ways ! Piwik platform has fewer bugs, fewer regressions, and we are able to release new minor and major versions frequently.

  Which parts of Piwik software are automatically tested ?

  • Piwik back-end in PHP5 : we use PHPUnit to write and run our PHP tests : unit tests, integration tests, and plugin tests.
  • piwik.js Tracker : the JS tracker is included into all websites that use Piwik. For this reason, it is critical that piwik.js JavaScript tracker always works without any issue or regression. Our Javascript Tracker tests includes both unit and integration tests.
  • Piwik front-end : more recently we’ve started to write JavaScript tests for the user interface partially written in AngularJS.
  • Piwik front-end screenshots tests : after each change to Piwik, more than 150 different screenshots are automatically taken. For example, we take screenshots of each of the 8-step installation process, we take screenshots of the password reset workflow, etc. Each of these screenshot is then compared pixel by pixel, with the “expected” screenshot, and we can automatically detect whether the last code change has introduced an undesired visual change. Learn more about Piwik screenshot tests.

  How often do we run the tests ?

  The tests are executed by Travis CI after each change to the Piwik source code. On average all our tests run 20 times per day. Whenever a Piwik developer pushes some code to Github, or when a community member issues a Pull request, Travis CI automatically runs the tests. In case some of the automated tests started failing after a change, the developer that has made the change is notified by email.

  Should I use Travis CI ?

  Over the last six years, we have used various Continuous Integration servers such as Bamboo, Hudson, Jenkins… and have found that the Travis CI is the ideal continuous integration service for open source projects that are hosted on Github. Travis CI is free for open source projects and the Travis CI team is very friendly and reactive ! If you work on commercial closed source software, you may also use Travis by signing up to Travis CI Pro.

  Summary

  Tests make the Piwik analytics platform better. Writing tests make Piwik contributors better developers. We save a lot of time and effort, and we are not afraid of change !

  Here is the current status of our builds :
  Main build :
  Screenshot tests build :

  PS : If you are a developer looking for a challenge, Piwik is hiring a software developer to join our engineering team in New Zealand or Poland.

• Piwik 1.12, New Features, API Improvements, Stability — The Last Piwik 1.X Release

  30 mai 2013, par Piwik team — Development

  We are very excited to announce the immediate availability of Piwik v1.12 !

  • Download Link
  • How to update Piwik ?
  • List of all tickets closed : Changelog

  Piwik v1.12 is a major new release with four big new features, seven smaller new features, several API improvements and all together 82 tickets fixed. This is also the last major 1.X release, which means after this release we will be working on releasing Piwik 2.0. This also means that you should upgrade to PHP 5.3 or higher if you haven’t already, since Piwik 2.0 will only support PHP 5.3 and above.

  Finally, this release contains two breaking changes to the API. If you use the Piwik API click here or scroll down to see if you’re affected.

  Table of Contents :

  1. New Big Feature – Beta Release Channel
  2. New Big Feature – Segment Editor
  3. New Big Feature – Page Speed Reports
  4. New Big Feature – Device Detection Reports
  5. Other Improvements
  6. API Changes and Improvements
  7. What we’re working on
  8. Participate in Piwik
  9. Summary

  New Big Feature – Beta Release Channel

  

  For those of you who want to help test Piwik 2.0-beta releases as soon as they come up, we’ve made it easier to use our beta releases. Navigate to the Settings > General Settings page and click the The latest beta release radio button. You will then be able to upgrade to beta releases.

  This isn’t truly a major feature, but we think it’s just as important because it will allow us to create more beta releases and thus catch more bugs before we make a final release. This means more releases and more stability for you.

  New Big Feature – Segment Editor

  

  The Segment Editor is a long-awaited new feature that allows you to view, save and edit your segments.

  Piwik has supported segmentation (filtering visits and reports by arbitrary criteria, like browser family) for quite some time now, but it has never been possible to visually create and modify them. Nor could they be saved for later recall.

  Thanks to the eighty individuals and company who funded this feature, it is now possible to :

  • visually segment your visitors, instead of creating URLs.
  • save segments and easily switch between them, instead of remembering URLs.
  • get suggestions for segments that might be helpful to view.
  • learn more in the Segmentating Analytics reports user documentation..

  New Big Feature – Page Speed Reports

  You can now see how long it took your webserver to generate and send pages over HTTP through the new Avg. Generation Time metric.

  This metric can be viewed on both the Pages and Page Titles reports :

  

  And the average page generation time for all the pages in your website/webapp is displayed on the visitors overview :

  

  You can use this new information to benchmark your webapp and web server.

  New Big Feature – Device Detection Reports

  Piwik 1.12 also includes a new plugin that provides reports on the device types (tablet, desktop, smartphone, etc.), device brands (Apple, Google, Samsung, etc.) and device models (iPad, Nexus 7, etc.) your visitors use to access your website :

  

  The new plugin also enhances Operating system detections (detecting sub versions of Linux, Windows, and more).

  Note : This plugin is not enabled by default, but will be in Piwik 2.0. If you want to view these reports now, you can activate the plugin in the Installed Plugins admin page. Navigate to Visitors > Devices to see the new reports. You may also use the new (beta) ‘Device type’.

  The new plugin was developed with the support of Clearcode.cc our technology partner

  

  Other improvements

  Majestic SEO Metrics

  

  We’ve added two new SEO metrics to the SEO widget, both of which are calculated by MajesticSEO.com. These metrics will tell you the number of external backlinks (the number of links to your site from other sites) and the number of referrer domains (the number of domains that link to your site).

  We thank the team at Majestic for their support and hard work in bringing you these metrics to your Piwik dashboards !

  Real-time Visitor Count Dashboard Widget

  

  There is now a simple new widget you can use to see the number of visitors, visits and actions that occurred in the last couple minutes. We call it the Real Time Visitor Counter !

  New segment parameter : siteSearchKeyword.

  There is now a new segment parameter you can use to segment your visits : siteSearchKeyword. This parameter will let you select visits that had site searches with a specific keyword.

  Ignore URL letter case when importing log files.

  We’ve added a new option to the log import script, –force-lowercase-path. When used, the importer will change URL paths to lowercase before tracking them. This way http://domain.com/MY/BLOG will be treated the same as http://domain.com/my/blog.

  Updated ISP Names

  

  We’ve also modified the Providers report so prettier and more up-to-date names of ISPs are displayed.

  Customize the background/text/axis color of graphs.

  

  It is now possible to change the background color, text color and/or axis color of the graph images generated by the ImageGraph plugin. To access this functionality, use the following URL query parameters when generating an image :

  • backgroundColor
  • textColor
  • axisColor

  For example :

  http://demo.piwik.org/index.php?module=API&method=ImageGraph.get&idSite=7&apiModule=UserSettings&apiAction=getBrowser&token_auth=anonymous&period=day&date=2013-03-21,2013-04-19&language=en&width=779&height=150&fontSize=9&showMetricTitle=0&aliasedGraph=1&legendAppendMetric=0&backgroundColor=efefef&gridColor=dcdcdc&colors=cb2026

  Send your users to a custom URL after they logout.

  If you manage a Piwik installation with many users and you want to send them to a custom page or website after they log out of Piwik, you can now specify the URL to redirect users after they log out.

  API Changes and Improvements

  BREAKING CHANGE – renamed segment parameters.

  The following segment parameters have been renamed :

  • continent renamed to : continentCode
  • browserName renamed to : browserCode
  • operatingSystem renamed to : operatingSystemCode
  • lat renamed to : latitude
  • long renamed to : longitude
  • region renamed to : regionCode
  • country renamed to : countryCode
  • continent renamed to : continentCode

  If you use one of the old segment parameter names, Piwik will throw an exception, so you should notice when you’re using an old name.

  BREAKING CHANGE – changes to the input & output of the Live.getLastVisitsDetails method.

  The following changes were made to the Live.getLastVisitsDetails API method :

  • The method no longer uses the maxIdVisit query parameter. It has been replaced by the filter_offset parameter.
  • Site search keywords are now displayed in a <siteSearchKeyword> element. They were formerly in <pageTitle> elements.
  • Custom variables with page scope now have ‘Page’ in their element names when displayed. For example, <customVariablePageName1>, <customVariablePageName2>, etc.

  Filter results of MultiSites.getAll by website name.

  It is now possible to filter the results of MultiSites.getAll by website name. To do this, set the pattern query parameter to the desired regex pattern.

  Get suggested values to use for a segment parameter.

  The new API method API.getSuggestedValuesForSegment can now be used to get suggested values for a segment parameter. This method will return a list of the most seen values (in the last 60 days) for a certain segment parameter. So for browserCode, this would return the codes for the browsers most visitors used in the last 60 days.

  Use extra tracking query parameters with the JS tracker (such as ‘lat’ & ‘long’).

  We’ve added a new method to the JavaScript tracker named appendToTrackingUrl. You can use this method to add extra query parameters to a tracking request, like so :

  _paq.push(['appendToTrackingUrl', 'lat=X&long=Y']);

  What we’re working on

  As we said above, Piwik v1.12 is the last in the 1.X series of releases. This means we are now officially working on Piwik 2.0.

  Piwik 2.0 will be a big release, to be sure, but it’s going to bring you more than just a couple new features and a bag of bug fixes. For Piwik 2.0 we will be revisiting the user needs and the ideals that originally prompted us to create Piwik in order to build our vision of the future of web analytics.

  Piwik 2.0 won’t just be a bigger, better web app, but a new platform for observing and analyzing the things that matter to you.

  Participate in Piwik

  Are you a talented developer or an experienced User Interface designer ? Or maybe you like to write documentation or are a marketing guru ?

  If you have some free time and if you want to contribute to one of the most awesome open source projects around, please get in touch with the Piwik team, or read this page to learn more…

  Summary

  For the full list of changes in Piwik 1.12 check out the Changelog.

  Thank you to the core developers, all the beta testers and users, our official supporters, the translators & everyone who reported bugs or feature requests. Also thank you to softwares we use, and the libraries we use.

  If you are a company and would like to help an important project like Piwik grow, please get in touch, it means a lot to us. You can also participate in the project —

  –> if you like what you read, please tell your friends and colleagues or write on your website, blog, forums, stackoverflow, etc. <–
  

  Peace. Enjoy !

• Anomalie #4128 : Bug de génération de boucle avec les modèles Spip

  11 avril 2018, par Julien PORIAU

  Salut,
  parfois le jeu de caractère "binaire" est visible uniquement dans le
  code source (ligne 1233). Mais on observe tout de même un soucis dans la
  mise en page.

  view-source:http://spip-dev.nidecker.com/probleme-de-langue.html?lang=ca

  Julien.

  Le 11.04.2018 à 14:28, redmine@spip.org a écrit :

  La demande #4128 a été mise à jour par b b.

  • Statut changé de /Nouveau/ à /En cours/
  • Priorité changé de /Haut/ à /Bas/

  Salut, peux-tu fournir le code du modèle en question ?

  De mon côté, je n’ai aucun problème sur la page que tu cites en exemple...

  ---

  Anomalie #4128 : Bug de génération de boucle avec les modèles Spip
  <https://core.spip.net/issues/4128#change-13824>

  • Auteur : Julien PORIAU
  • Statut : En cours
  • Priorité : Bas
  • Assigné à :
  • Catégorie : code généré
  • Version cible : 3.2
  • Resolution :
  • Navigateur : Firefox

  Dans les modèles personnalisés Spip, les images (boucle documents ou
  logos) sont mal générées et provoque un bug d’encodage visible dans le
  front-end lors du passage dans une autre langue (balises multi).
  Nous n’avons pas trouvé où était le souci dans Spip, mais les
  caractères qui remontent dans le code source, ressemblent aux octets
  qui composent le fichier binaire d’une image.
  Voir en live ici :
  http://spip-dev.nidecker.com/probleme-de-langue.html?lang=ca.

  Pour essayer d’isoler cette anomalie, nous avons procédé de la sorte
  avec l’aide de mon développeur :

  1. Nous sommes reparti d’un SPIP 3.1.7 entièrement neuf (minimal),
  avec deux modèles Spip, rien d’autre.
  Le bug se reproduit, ce qui exclus un problème lié aux squelettes ou
  autres plugins.

  Nous n’avons pas réussi a déterminer précisément ce qui génère ce bug,
  à part que c’est dans un contexte où on appelle une langue pas définie
  dans le multi.
  En fonction du contenu de l’article, du nombre de modèles dans
  l’article, en fonction des boucles dans les inclure, le bug n’arrive
  pas au même endroit...

  Le problème vient de la génération des logos ou documents : si on
  supprime les balises |#LOGO_*| ou si on renomme |IMG| en |IMG_|, plus
  d’erreur.
  Même sans traitements, avec juste |[(#LOGO_*)]|, rien à faire.

  2. Nous avons pensé que c’était peut être une image au mauvais format :
  On a alors tenté de passer |ImageOptim| sur tout le répertoire |/IMG|,
  redimensionné tous les logos en vignettes png de 320x240, rien à faire...

  3. On a fini par passer ce site de test en 3.2, pas mieux.

  4. Nous avons épluché les caches générés dans |/tmp/cache| et
  |/tmp/cache/skel|, tout paraît normal de ce côté là..

  5. On a ensuite un peu avancé en enlevant dans |mes_options.php| la
  variable |$GLOBALS[’forcer_lang’] = true|".
  Sur la version minimal, plus de bug. Mais sur le site de production,
  le problème réside toujours.
  Mais en faisant des tests avec et sans (et en supprimant bien
  |/tmp/cache/| à chaque fois), ça se confirme pour la version minimal.

  6. A partir d’une copie de la version production, nous avons désactivé
  tout les plugins, passer |ImageOptim| sur |/IMG| et rien a faire..
  Impossible de déterminé d’où vient le problème :(

  7. Nous avons essayé d’écrire comme ceci : |[src="(#LOGO_MOT|image_reduire50,*|extraire_attributsrc)" alt="">]|
  Cela fonctionne sur la version minimal mais pas sur la version production.

  8. Dans la version minimal, j’ai encore récemment testé une dernière
  chose. J’ai supprimé les documents non sollicités sur ma page de teste
  (spip.php ?article1441&lang=ca).
  Avec la requête SQL suivante : |DELETE FROM jones_documents WHERE
  id_document NOT IN
  (1948,1949,2534,2535,630,631,1783,1784,1785,1786,1787,1788,1781,1782)|
  Le bug n’apparait plus..

  Je sèche..

  Vous trouverez ici en téléchargement une archive de la version minimal
  (Spip 3.1.7) :
  https://www.dropbox.com/s/dek0zg7jafl8uxe/jones.zip?dl=0] ( 20mo)
  Pour reproduire le bug, il suffit de passer la variable "&lang=ca"
  dans l’article 1441 (localhost/spip.php ?article1441&lang=ca).

  Je donne volontiers un accès à la version production si besoin.

  ---

  Vous recevez ce mail car vous êtes impliqués sur ce projet.
  Pour changer les préférences d’envoi de mail, allez sur
  http://core.spip.org/my/account

  ---
  L’absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
  https://www.avast.com/antivirus