reprosser
3 years agoOccasional Contributor
Best Practice - Enviroments coverage in Reports
We run all our test cases against OS (windows and linux), http and HTTPS, and Browser (Edge and Chrome). (the test is the same for each option) One way to keep track is to set up environment pick lis...
- 3 years ago
Hi Rick,
If you were to go with the option of naming the cycles by the environment, you can use the Cycles page itself as a high level dashboard/report - I've attached an example of how I used it in my last project. There's a lot of useful information in the Cycles page:
- Total tests to execute
- Issues reported
- Progress % (with status breakdown when you hover)
- Cycle status (you can add your own custom statuses such as 'Blocked')
- And you'll see I included a custom field (Blockage) that I used to report at a high level any issues with the cycle (or environment in your case).
I found it very useful for managing the various test cycles at a glance.
Hope it helps.
Best, Andy