Actions

Difference between revisions of "System Tests Working Group"

From Joomla! Documentation

(Improvements in current tests)
Line 21: Line 21:
 
* '''(done)''' Create an Assert in all test that makes sure there is not any warning, even if the test passes. See this example:{{-}}[[File:System tests-example of warning.png|450px]]{{-}}
 
* '''(done)''' Create an Assert in all test that makes sure there is not any warning, even if the test passes. See this example:{{-}}[[File:System tests-example of warning.png|450px]]{{-}}
 
* '''(done)''' Create a graphical test coverage report  
 
* '''(done)''' Create a graphical test coverage report  
* Move to Codeception framework
+
* 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
  

Revision as of 06:31, 28 July 2014

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


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/

Documents