[#45992] - Added end-to-end test support using testRigor
- Pending
- Medium
- Build: 5.3-dev
- # 45992
- Diff
- amandassa-tR:add-e2e-tests
User tests: Successful: Unsuccessful:
Summary of Changes
Included end-to-end testing support using testRigor, located on the folder tests/end-to-end. It contains 10 test cases for multiple functionalities.
Testing Instructions
- GitHub Actions: Automated workflow in .github/workflows/joomla-install-test.yml that:
- Installs the Joomla! cms locally
- Runs testRigor test suites against
localhost:8080 - Uses GitHub secrets for authentication (
CI_TOKENandSUITE_ID)
- testRigor CLI: Executes test cases written in natural language on the testRigor platform.
Actual result BEFORE applying this Pull Request
Tests are currently not written in plain english, the current test status is not visible outside of github and the maintenability for those tests is lower.
Expected result AFTER applying this Pull Request
Adds end-to-end testcases that can easily be modified/executed using testRigor's CLI tool or testRigor's website.
Test cases in plain english are easier to maintain and to contribute in an open source environment.
Link to documentations
Please select:
- Documentation link for docs.joomla.org:
- No documentation changes for docs.joomla.org needed
- Pull Request link for manual.joomla.org:
- No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Repository Unit Tests |
- The test cases written in testrigor are easier to maintain (UI changes don't affect test cases).
- On the other hand it's also easier for people to contribute since the test cases are simpler to write (as the steps are written in plain English).
But there is a huge amount of work to be done just to get testrigor covering everything we already have tests for before we could see any increase in test coverage
What are the advantages to switching from the already existing cypress tests to using testrigor and writing all new tests?