microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2025-12-10 14:16:15 -06:00
Code Issues Packages Projects Releases 177 Wiki Activity

Improve test plan item wiki

Sandeep Somavarapu 2023-06-27 12:58:08 +02:00
parent a8c3ca0bb0
commit 4557c52841
1 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Writing-Test-Plan-Items.md

@ -1,8 +1,19 @@
## Test Plan Items
# Test Plan Items
Test Plan Item (TPI) is an issue created with label `testplan-item` for testing the feature during the endgame. It shall define the platforms it needs to be tested against and also how complex (1-5) it is to test.
**Note:** A Test Plan Item shall not take too long to test and scoped to a specific feature. Please note that **Complexity 5 is not unlimited and there shall be a time scope of one or two hours max of testing**. If your Test Plan Item has multiple features to test and also goes beyond complexity 5 and time scope, please break it down into multiple complexity (1-5) test plan items.
## Good Practices
- Write the Test Plan Item with the mind set of a tester, one who does not know anything about the feature. If it involves setting up an environment then elaborate the set up instructions in a separate **Set up** section. It is recommended to provide as much context as possible for the tester to understand the feature and test it effectively.
- A Test Plan Item shall not take too long to test and scoped to a specific feature. Please note that **Complexity 5 is not unlimited and there shall be a time scope of one or two hours max of testing**. If your Test Plan Item has multiple features to test and also goes beyond complexity 5 and time scope, please break it down into multiple complexity (1-5) test plan items.
- Consider to write a Test Plan Item
- For any feature that will take considerable time to test or set up
- For any feature that you are looking for exploratory testing
- For any refactorings you did during the milestone and expecting sanity/regression/smoke testing in that area.
## Test Plan Item format
There is a tool that parses all these TPIs and generates user assignments. Endgame master uses this tool to assign these TPIs to others for testing. A Test Plan Item should contain **Header** and **Body** sections which are separated by `---` (line). Header section shall contain the meta information about the TPI that is used by the tool for generating TPI assignments. Body section shall include testing details for the user to test.