From 876d42dac51533d9ecb4c434b98b71dc5df358ac Mon Sep 17 00:00:00 2001 From: traviswindsormoodle Date: Tue, 25 Aug 2026 16:10:15 +0800 Subject: [PATCH 1/2] Revise QA testing steps and workflow actions Updated QA testing process with new workflow actions and guidelines. --- general/development/process/testing/qa.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/general/development/process/testing/qa.md b/general/development/process/testing/qa.md index f5199c079..6d36e60ed 100644 --- a/general/development/process/testing/qa.md +++ b/general/development/process/testing/qa.md @@ -23,13 +23,15 @@ Would you like to help with QA testing? If so, please make sure you have created - Only assign an issue to yourself which no one else is testing (Assignee = Unassigned). - Only assign one issue at a time unless you plan to test a number of related issues within the next 24 hours. In other words, don't assign several issues to yourself then do nothing for several days. ;-) - The label `test_server_required` indicates issues that can't be tested on the QA testing site. The label `credentials_required` indicates that credentials such as an OAuth 2 service client ID and secret are required. -2. Using either the [Moodle QA Testing Site](https://qa.moodledemo.net/) or your own test site running the latest Moodle 4.2dev (available from Git on the integration/main branch git://git.moodle.org/integration.git) with [debugging](https://docs.moodle.org/dev/debugging) set to developer, perform each of the steps listed in the test. -3. Please *attach screenshots of the steps where you verify or check something*. -4. If it makes sense, please test using the currently supported themes, Boost and Classic. -5. Choose an appropriate workflow action: +2. When you are ready to start testing a particular test case, select the workflow action "Start Testing". If you decide that you can't perform the test, then you just select the workflow action "Cancel testing" and the test will go back into the test backlog, available for testing. +3. Using either the [Moodle QA Testing Site](https://qa.moodledemo.net/) or your own test site running the latest Moodle 4.2dev (available from Git on the integration/main branch git://git.moodle.org/integration.git) with [debugging](https://docs.moodle.org/dev/debugging) set to developer, perform each of the steps listed in the test. +4. Please *attach screenshots of the steps where you verify or check something*. +5. Please test using the currently supported Boost theme. +6. Choose an appropriate workflow action: - `Pass` - Test runs perfectly. Add comment such as feedback about a new feature, browsers used for testing (if applicable; example: "This test passes on Q&A site with Teacher role using Boost theme"), or simply "This test passes - yippee!" - `Fail` - Something doesn't work, or you obtain debugging messages. Add comment describing the step that doesn't work. If in doubt whether to pass a test, give it a fail and add a comment describing your doubts. - `Obsolete` - Test is no longer relevant in the current Moodle version. Add comment explaining why. + - `Hold` - Test shouldn't be executed in this current test run. Add a comment explaining why. It would be worth raising this in the QA chat [#qa:moodle.com](https://matrix.to/#/#qa:moodle.com) room on Matrix :::info[Out of date tests] @@ -248,6 +250,7 @@ If you have any questions or comments, please post in the [Testing and QA forum] Comments on tests from previous QA cycles: +- [Moodle 5.1 QA](https://moodle.atlassian.net/browse/MDLQA-21163) - [Moodle 5.1 QA](https://moodle.atlassian.net/browse/MDLQA-20667) - [Moodle 5.0 QA](https://moodle.atlassian.net/browse/MDLQA-19836) - [Moodle 4.5 QA](https://moodle.atlassian.net/browse/MDLQA-18925) From 907a62dbd8eb72623876f8f7af008f3183b5d7c3 Mon Sep 17 00:00:00 2001 From: traviswindsormoodle Date: Tue, 25 Aug 2026 16:18:56 +0800 Subject: [PATCH 2/2] Squashed commit from review Fix formatting in QA testing guidelines Fixed grammar Fix formatting for workflow actions in QA.md Updated formatting for workflow actions in QA testing instructions. Update Moodle QA cycle links Typo for 5.2 Fix formatting and clarify QA testing instructions Removed whitespace --- general/development/process/testing/qa.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/general/development/process/testing/qa.md b/general/development/process/testing/qa.md index 6d36e60ed..cc838dfa3 100644 --- a/general/development/process/testing/qa.md +++ b/general/development/process/testing/qa.md @@ -23,7 +23,7 @@ Would you like to help with QA testing? If so, please make sure you have created - Only assign an issue to yourself which no one else is testing (Assignee = Unassigned). - Only assign one issue at a time unless you plan to test a number of related issues within the next 24 hours. In other words, don't assign several issues to yourself then do nothing for several days. ;-) - The label `test_server_required` indicates issues that can't be tested on the QA testing site. The label `credentials_required` indicates that credentials such as an OAuth 2 service client ID and secret are required. -2. When you are ready to start testing a particular test case, select the workflow action "Start Testing". If you decide that you can't perform the test, then you just select the workflow action "Cancel testing" and the test will go back into the test backlog, available for testing. +2. When you are ready to start testing a particular test case, select the workflow action `Start Testing`. If you decide that you can't perform the test, then you just select the workflow action `Cancel testing` and the test will go back into the test backlog, available for testing. 3. Using either the [Moodle QA Testing Site](https://qa.moodledemo.net/) or your own test site running the latest Moodle 4.2dev (available from Git on the integration/main branch git://git.moodle.org/integration.git) with [debugging](https://docs.moodle.org/dev/debugging) set to developer, perform each of the steps listed in the test. 4. Please *attach screenshots of the steps where you verify or check something*. 5. Please test using the currently supported Boost theme. @@ -31,7 +31,7 @@ Would you like to help with QA testing? If so, please make sure you have created - `Pass` - Test runs perfectly. Add comment such as feedback about a new feature, browsers used for testing (if applicable; example: "This test passes on Q&A site with Teacher role using Boost theme"), or simply "This test passes - yippee!" - `Fail` - Something doesn't work, or you obtain debugging messages. Add comment describing the step that doesn't work. If in doubt whether to pass a test, give it a fail and add a comment describing your doubts. - `Obsolete` - Test is no longer relevant in the current Moodle version. Add comment explaining why. - - `Hold` - Test shouldn't be executed in this current test run. Add a comment explaining why. It would be worth raising this in the QA chat [#qa:moodle.com](https://matrix.to/#/#qa:moodle.com) room on Matrix + - `Hold` - Test isn't ready to run yet, usually because its blocked by another issue. Add a comment explaining why its blocked and what that issue is. Testers shouldn't pickup any test that's been marked as `On Hold`. :::info[Out of date tests] @@ -250,7 +250,7 @@ If you have any questions or comments, please post in the [Testing and QA forum] Comments on tests from previous QA cycles: -- [Moodle 5.1 QA](https://moodle.atlassian.net/browse/MDLQA-21163) +- [Moodle 5.2 QA](https://moodle.atlassian.net/browse/MDLQA-21163) - [Moodle 5.1 QA](https://moodle.atlassian.net/browse/MDLQA-20667) - [Moodle 5.0 QA](https://moodle.atlassian.net/browse/MDLQA-19836) - [Moodle 4.5 QA](https://moodle.atlassian.net/browse/MDLQA-18925)