Automated Tests Working Group: Difference between revisions

From Joomla! Documentation

← Older editNewer edit →
MATsxm (talk | contribs)
Email Confirmed, JDOC Contributors, Translator
34,129 edits
No edit summary
Update for 2017
Line 9: Line 9:


== Roadmap==
== Roadmap==
The next steps in this team are:
The next steps for 2017 / 2018 are:


=== GSoC 2014 ===
* System test coverage for Joomla! CMS core
* focus on [[GSOC_2014_Project_Ideas#Project:_Webdriver_system_tests_for_CMS|Google Summer of Code 2014 Project: Webdriver_system_tests_for_CMS]]
* Update PHPUnit to newest version
* Code Sniffer rules
* New docker based infrastructure
* Extension Tests for B/C


=== Sauce Labs integration ===
==History==
* 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 ===
=== GSoC 2016 ===
* '''(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]]{{-}}
* JavaScript Tests with Karma and Jasmine JS
* '''(done)''' Create a graphical test coverage report
* focus on Joomla system Tests and test architecture for Joomla
* 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.
** 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 ===  
=== GSoC 2014 ===
We have Travis complaining about this:
* focus on [[GSOC_2014_Project_Ideas#Project:_Webdriver_system_tests_for_CMS|Google Summer of Code 2014 Project: Webdriver_system_tests_for_CMS]]
<source lang="php">
E.................E.........
I'm sorry but your test run exceeded 50.0 minutes.
One possible solution is to split up your test run.
</source>
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 ==
== Documents ==
* Joomla! Testing Overview session slides: https://www.slideshare.net/YvesHoppe/joomla-testing-jdd-germany-2016
* [[Writing_System_Tests_for_Joomla!_-_Part_1|Writing System Tests for Joomla!]]
* [[Writing_System_Tests_for_Joomla!_-_Part_1|Writing System Tests for Joomla!]]
* GSOC-Webdriver_system_tests_for_CMS repository: https://github.com/joomla-projects/GSOC-Webdriver_system_tests_for_CMS
* GSOC-Webdriver_system_tests_for_CMS repository: https://github.com/joomla-projects/GSOC-Webdriver_system_tests_for_CMS
Line 51: Line 34:


== Projects ==
== Projects ==
* com_localise: https://github.com/joomla-projects/com_localise/tree/codeception project for testing a Joomla extension with Codeception framework adding parallel testing and Saucelabs or BrowserStack integration.
* com_weblinks: https://github.com/joomla-extensions/weblinks - Extension testing project with Codeception
* https://github.com/joomla-projects/Codeception/ fork of original Codeception project for bug fixing and contributing to the main project.
* Joomla core system tests: https://github.com/joomla-projects/gsoc16_browser-automated-tests
* Basic steps and actions for Joomla Selenium / Codeception tests: https://github.com/joomla-projects/joomla-browser
* JoRobo build scripts for building extensions: https://github.com/joomla-projects/jorobo
* Joomla Robo.li testing scripts: https://github.com/joomla-projects/joomla-testing-robo
* The Joomla [[Docker Container for System Tests]]
* The Joomla [[Docker Container for System Tests]]
* Docker system testing image: https://github.com/joomla-projects/docker-systemtests
* JS Tests (merged in core): https://github.com/joomla-projects/gsoc16_js-unit-tests
* Joomla vagrant testing box: https://github.com/joomla-projects/vagrant-joomla-testing Groups
* Selenium package with webdrivers: https://github.com/joomla-projects/selenium-server-standalone


[[Category:Working Groups]]
[[Category:PLT]]
[[Category:PLT]]
[[Category:Automated Testing]]
[[Category:Automated Testing]]

Revision as of 17:38, 17 February 2017

This is the home page of the Automated Test Working Group, that is the result of combining the old System Testing Working Group and the Unit Testing Working Group.

Team Members

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

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 for 2017 / 2018 are:

  • System test coverage for Joomla! CMS core
  • Update PHPUnit to newest version
  • Code Sniffer rules
  • New docker based infrastructure
  • Extension Tests for B/C

History

GSoC 2016

  • JavaScript Tests with Karma and Jasmine JS
  • focus on Joomla system Tests and test architecture for Joomla

GSoC 2014

Documents

Projects

Retrieved from "https://docs.sandbox.joomla.org/index.php?title=Automated_Tests_Working_Group&oldid=365383"