Actions

Difference between revisions of "System Tests Working Group"

From Joomla! Documentation

m (added Category:PLT using HotCat)
m (Improvements in current tests: helping with page)
Line 19: Line 19:
  
 
=== Improvements in current tests ===
 
=== Improvements in current tests ===
* '''(done)''' Create an Assert in all test that makes sure there is not any warning, even if the test passes. See this example:
+
* '''(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]]{{-}}
[[File:System tests-example of warning.png|thumbnail]]  
+
 
* '''(done)''' Create a graphical test coverage report  
 
* '''(done)''' Create a graphical test coverage report  
 
* Move to Codeception framework
 
* Move to Codeception framework

Revision as of 04:57, 25 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

  • (done) Create an Assert in all test that makes sure there is not any warning, even if the test passes. See this example:
    System tests-example of warning.png
  • (done) Create a graphical test coverage report
  • Move to Codeception framework
  • Create a Best Practice in System testing Joomla! extensions with https://github.com/joomla-projects/com_localise component

Documents