Below is a sample Test Plan structure which I created before for some project.
1. Background
2. Purpose of this Document
3. Reference
4. Features to be Tested
5. Features not to be Tested
6. Test Approach
7. Test Item Configurations
7.1 Rack Configuration
7.2 Platform Configurations for Each Testing Item
7.3 Environment Locale to be Tested
8. Resources
8.1 Human Resources
8.2 Hardware Resources
8.3 Software Resources
9. Test Cycle and Schedule
10. Risks
11. Assumptions
12. Test Entrance/Exit Criteria
12.1 Entrance Criteria
12.2 Exit Criteria
13. Defects Reporting
14. Contacts
執行優先於整理,不要憑空設計系統:以我的防彈筆記法實踐為例
-
之前分享如何設計標籤的文章(如何用標籤管理上萬則筆記?Evernote, Notion, obsidian 都適用
),有讀者提問說:「標籤的使用對我來說有點抽象😂,可能因為情境總是難以明確的定義?常常會覺得同一個任務又具有每日推進的性質、但也具有思考醞釀的性質,結果在下標籤的時候就猶豫不決,不知道您是否曾...
5 小時前
0 Comments:
張貼留言