How to add steps to reproduce to a bug report
Note: You are currently viewing documentation for Moodle 2.9. Up-to-date documentation for the latest stable version of Moodle may be available here: How to add steps to reproduce to a bug report.
Often a bug reporter is a developer or/and an expert Moodle user. By consequence he forgets to add the test steps into the description.
When you know how to reproduce/test a bug in Moodle, please indicate these test steps. The steps should explain to a Moodle user (not a developer) how to see the problem in Moodle.
- the developer will be happy: the steps are very useful for the developer in order to reproduce/test your issue. Think that sometimes the developer has the ability to fix a bug, but doesn't have yet your knowledge about the module containing this bug.
- the QA manager will be even more happy: if you indicate the test steps, any QA tester would be able to retest and validate the fix during the weekly quality assurance process.
Example of test steps
Environment: Moodle 2.0 - Server run on Linux/Apache/MySQL
1. Connect as Admin
2. Go to a Course page > Turn editing on > Select Insert Label operation > Enter some details and Save
=> The new label is not displayed into the course page
Expected result: a newly created label should be displayed into a course page