Wiki » History » Revision 10
Revision 9 (zcjia, 2022-10-14 06:57) → Revision 10/11 (zcjia, 2022-10-14 06:58)
# Test cases migrate and maintain guideline ## Overall test case structure ### Acceptance testing * We will have a parent task for all acceptance test cases: https://progress.opensuse.org/issues/117445 https://progress.opensuse.org/issues/116974 * We will add sub tasks under the parent task ### Regression testing * We will have a parent task for all regression test cases: https://progress.opensuse.org/issues/117442 * We will use category to mark if the test case has already been automated * We will use parent-sub task mode to mark the specific component * We will use the target version field to mark which release we are testing ### The format of the subject * The subject should be started with [Regression] OR [Acceptance] > For [Regression] test cases, the second key word should be the component of the test case, e.g [NetworkManager] > For [Acceptance] test cases, the second and third key word should be the exact milestone and build number. e.g [Alpha4][151.1] * The priority of the ticket > P0 -> Immediate > P1 -> Urgent > P2 -> High > P3 -> Normal > P4 -> Low ### The status of the ticket/ test case: * The default of the test case is NEW * The test case will be marked as RESOLVED when test passed, * The test case will be marked as REJECTED if there's any critical bugs found * The corresponding SUT build number should be included in the comment when updating the status ## Test preparation * Before regression test execution, we always clone the regression test tickets used by the last release as a base for the upcoming release. * Before acceptance test execution for each milestone, we clone acceptance tickets from https://progress.opensuse.org/issues/116974