Acceptance testing/Contributing automated tests
The issue MDLQA-1 contains testing tasks required to manually test many of the features and functions of Moodle.
We are aiming to automate as many of these tests as possible using Moodle's new behat-based testing framework, so that they can be run weekly, and so that real users can focus on more exploratory testing instead. Currently there are over 400 MDLQA tests, so help in automating them is much appreciated!
Automating a test
- Choose a test from the list MDLQA tests with label mdlqa_conversion.
- Create a new MDL issue with summary 'Automate MDLQA-wxyz' and component 'Automated functional tests' and any MDLQA component such as 'Forum' which is also an MDL component.
- Add the mdlqa_conversion label to the new MDL issue
- Link to the MDLQA test by selecting 'Will help resolve' as the link type.
- Follow the instructions provided in the guide Writing acceptance tests.
- Include 'MDLQA-wxyz' and a short description of what is being automated to the commit message/s where the .feature files are added/edited.
Many thanks for helping with test automating!
New features with acceptance tests
- Issues should be linked to new QA issue as "is a QA test written for"
- QA issue should be marked with priority blocker
Choosing QA tests for automating
To decide if a QA test can be automated we ask:
- Does it require any third-party servers or infrastructure e.g. OAuth 2 or CLI scripts?
- Does it require a person to detect if something is 'correct' vs. present/absent on the page e.g. drag and drop functionality?
If the answer to both questions is no, then it is likely that the QA test can be automated.
New features and improvements which cannot have an automated test written for them should be labelled qa_test_required and detailed testing instructions provided which can then be used when writing a new MDLQA test.