Difference between revisions of "System Tests Working Group"

From Joomla! Documentation

(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
* Puneet Kala (Working Group Coordinator)
 
* Puneet Kala (Working Group Coordinator)
 
* Javier Gómez (PLT liaison: javier.gomez at commmunity.joomla.org)
 
* Javier Gómez (PLT liaison: javier.gomez at commmunity.joomla.org)
* Kshitij Sharma
+
* Kshitij Sharma (member)
* Tanaporn Pantuprecharat
+
* Tanaporn Pantuprecharat (member)
* Mark Dexter
+
* Mark Dexter (advisor)
* Milton Bryant
+
* Milton Bryant (member)
* Niels Braczek
+
* Niels Braczek (member)
 +
* David Jardin (Infraestructure & servers)
 +
* Viktor Vogel (Infraestructure & servers)
 +
 
 +
See the full list at: http://volunteers.joomla.org/working-groups/system-tests-working-group
  
 
== Goals ==
 
== Goals ==
Line 27: Line 31:
 
* '''(done)''' Create a graphical test coverage report  
 
* '''(done)''' Create a graphical test coverage report  
 
* Move to Codeception framework. Some tests are being done here: https://github.com/joomla-projects/com_localise/tree/codeception#testing-with-codeception
 
* Move to Codeception framework. Some tests are being done here: https://github.com/joomla-projects/com_localise/tree/codeception#testing-with-codeception
* Create a Best Practice in System testing Joomla! extensions with https://github.com/joomla-projects/com_localise component
+
* Create a Best Practice in System testing Joomla! extensions with https://github.com/joomla-projects/com_localise component.
 +
** reorganise folders inside codeception for _step objects and _pages (we need to wait for Codeception 2.1, see: http://phptest.club/t/issue-with-codeception-autoload-and-namespaces/192 )
 +
** Run tests in parallel, see: https://twitter.com/JAVI_GOMEZ/status/523422301384368128
  
 
=== Travis ===  
 
=== Travis ===  
Line 42: Line 48:
  
 
After com_localise our efforts will be moved to com_weblinks https://github.com/joomla-extensions/weblinks/issues/10
 
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 ==
 
== Documents ==

Revision as of 04:37, 13 November 2014

Team Members[edit]

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

See the full list at: http://volunteers.joomla.org/working-groups/system-tests-working-group

Goals[edit]

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

Roadmap[edit]

The next steps in this team are:

GSoC 2014[edit]

Sauce Labs integration[edit]

  • 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[edit]

Travis[edit]

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[edit]

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[edit]

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[edit]

Projects[edit]