Actions

System Tests Working Group

From Joomla! Documentation

Contents

Team Members

  • Puneet Kala (Working Group Coordinator)
  • Javier Gómez (PLT liaison: javier.gomez at commmunity.joomla.org)
  • Kshitij Sharma
  • Tanaporn Pantuprecharat
  • Mark Dexter
  • Milton Bryant
  • Niels Braczek
  • David Jardin
  • Viktor Vogel

Goals

  • to improve the Quality of Joomla CMS software
  • to create learning material about "how to test" for the Joomla Community

Roadmap

The next steps in this team are:

GSoC 2014

Sauce Labs integration

  • Test SauceLabs and Travis integration with the repo at GitHub: https://saucelabs.com/opensource/travis. It will require the use of Paratest, to run several tests at the same time, otherwise it will take too long (more than 8 hours just the /Adminitrator/ tests)

Improvements in current tests

Travis

We have Travis complaining about this:

E.................E.........
I'm sorry but your test run exceeded 50.0 minutes. 
One possible solution is to split up your test run.

We need to find a solution, for example: http://blog.travis-ci.com/2012-11-28-speeding-up-your-tests-by-parallelizing-them/

Test Joomla extension

The goal of this project is to test com_localise extension https://github.com/joomla-projects/com_localise/ to create a proof of concept and documentation to teach others how to test their Joomla Extensions.

After com_localise our efforts will be moved to com_weblinks https://github.com/joomla-extensions/weblinks/issues/10

Create a infrastructure for fast testing the CMS

We plan to run create a battery of webservers able to run several instances of the system tests with different configuration: browser, screen size, testing area...

The idea is to create a server infraestructure capable to create a set of virtual machines and run individually part of the system testing suite on each of them. Then send a signal back to issues.joomla.org to change the status of a pull request to OK or KO depending on the result of running the tests.

Documents

Projects