This is the place to put links to all of your testing environments
1.
| | ALPHA | BETA | GAMMA | PRODUCTION |
| Backend Tool | n/a | n/a | n/a | n/a |
| Backend Tool | n/a | n/a | n/a | n/a |
| Backend Tool | n/a | n/a | n/a | n/a |
| Store Front | n/a | n/a | n/a | n/a |
2.
3.
| | ALPHA | BETA | GAMMA | PRODUCTION |
| Internet Explorer | | | | |
| Mozilla Firefox | | | | |
| Mac Safari | | | | |
Place links to your various defect reports here. For example, you could have a link of:
a. all defects assigned in your name
b. all defects assigned to QA
c. all defects of a particular release
d. all defects assigned to your subordinates
e. all defects of a particular part of the project (maybe hot topics)
f. etc...
Organize your links in ways that will help you stay organized. Organize your links in ways that will help you get your job done faster. You could just bookmark them in the tool itself, but I always like having ONE place where I can access everything from. My WIKI is my command center.
This is where you put links to your product’s hot topics. It’s valuable to be clear on which parts of your product are considered most important or most critical. This is good business and good testing practice. The reason for this is two-fold:
1. You will want to spend quality time and attention to the hot topics of your project because they are usually
a. the core of the functionality of your project and/or
b. buggy or risky parts of the code and/or
c. very visible to the client
2. The reality of testing is that you will run out of time. You will either run out of time before you have completed your initial testing of your project OR you will run out of time when running regression tests after yet another round of bug fixing development improvements.
You will want to focus on your hot topics in such moments.
This is where you link to your project’s test suites/test cases/test harnesses for easy access and execution.