Table of contents
In the longer run the goal is to have our own Selenium testing infrastructure (which include the dashboard), but for now we have decided to use Saucelabs which provide Selenium infrastructure where we can set up testing for the tiki.org sites.
Pascal will contact Saucelabs to get it setup.
Also, we will need to do:
1) Document how to record tests using Selenium IDE (a Firefox plugin) to record tests. (Alain assigned)
2) Document where to share tests. Wiki pages will be fine for now but the idea is to have them with SVN but see next point (Alain)
3) Document how to get them into a "test suite" which will be run by the Saucelabs testing infrastructure (Alain)
4) Start creating tests for the tiki.org sites, especially doc or dev. (Let's get everybody together for this).
5) Longer term roadmap to have tests committed together with features in SVN (but since this would require getting instances to a certain configuration and with test content to run the tests from, it is dependent on the Configuration Management and Systems Orchestration project to be done first.
6) Once the above is setup, Amette will figure our a way to automate SVN bisect to identify track what commit is behind which error.
7) Perhaps this can automatically be run on another machine on any error and the results inserted into a tracker on quality.tiki.org. Nelson will have coordinate with LPH how to insert it automatically into the specified tracker, probably by calling the AJAX tiki server,
Types of users
Make sure that use scenarios which are critical for their customers continue to work on trunk.
Need to do:
Tiki Testing Power User