Recherche avancée

Sur d’autres sites (6271)

• 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.

• Analytics for ePortfolios, Mahara hui conference

  20 mars 2014, par Matthieu Aubry — Community, Meta

  I was privileged to present at the Mahara Hui conference in Wellington, New Zealand.

  Here are the slides of my presentation “Analytics for ePortfolios” :

  Summary : by using an analytics tool that integrates well with Mahara, such as Piwik, Mahara users can benefit from a multitude of insightful analytics reports.

  Learn more

  Mahara is a web application to build your electronic portfolio. You can create journals, upload files, embed social media resources from the web and collaborate with other users in groups. Mahara is a popular open source project built by a passionate community, and used in universities, schools and companies all over the world.

  Mahara Hui is the first kiwi conference on Mahara, the open source ePortfolio system, in New Zealand. This 2-day conference was held at Te Papa in Wellington from 19 to 20 March 2014 (schedule)

  Next steps

  I’m excited to join the Mahara team at the Mahara Hui Hackfest organised today at Catalyst IT offices. We will brainstorm how to integrate Piwik beautifully within Mahara, and how to ultimately provide students and employees useful analytics on all the content they create !

• Piwik IRC Meetup on Tuesday

  10 février 2014, par Fabian Becker — Community, Development

  With the release of Piwik 2.0 and the Piwik Marketplace we are focusing on the community aspect of Piwik Development. In order to give users and developers a chance to get involved in Piwik we decided to have IRC meetups every two weeks, where we discuss current and future plans of Piwik development.

  Why should I join ?

  This is the chance for everyone to directly talk to developers and discuss issues and feature ideas. It is also good if you want to get involved in development and pick up smaller features to get to know the code base.

  Next Piwik meetup

  • Date : Tuesday February 11th, 7.30pm UTC
  • Duration : 30min
  • IRC #piwik channel (irc.freenode.net)

  Topics are :

  • 2.1 release (closed tickets)
  • open tickets for Piwik 2.2

  To join the chat, you can use the website : http://webchat.freenode.net/ (or join with your IRC client of choice) – See also what will be the time in your country at 7.30pm UTC. You will find us in the Freenode channel #piwik.