As a standard flow for reviewing and testing based on release notes, we propose a number of customization adjustments. These customizations relate to requirements. Note that customization changes apply to your entire Testersuite environment. So if you only have one environment, then this customizing will apply to all your current and future Test cycles.
1. Adjust default names of fields and statuses
A number of fields related to requirements need to be renamed. Please follow the list below:
- Rename the default field 'Tester' to 'Assessor'
- Rename the default field 'Developer' to 'Tester'
- Rename the status 'Ready for test' to 'Review'
- Rename the status 'In development' to 'Ready for test'
- Put 'Review' status above 'Ready for test' status
These changes change the default requirements testing tile on the dashboard to a requirements review tile. See image below.
2. Adding and removing statuses
In addition to renaming two default statuses (see previous point), at least the following two statuses must be added: Test OK and Test NOK. In addition, check that the list of statuses is complete and remove any statuses that are not relevant to your workflow.
3. Adjust email rules.
Edit the email rules for requirements to match the image below.
4. Add the value 'Release note' to the 'Type of requirement' field
You can use this field to indicate that the requirement is a release note.
5. Optional: add 'Note type' field
Optionally add a drop-down list field 'Note type' to requirements, using as options values that the supplier/customer recognizes. For example:
6. Add any other fields applicable in the release notes
Depending on the information in the provided release notes, you may choose to include this information in separate Testersuite fields. for example:
- Fields of type 'Text field large' for release note data such as 'Current operation', 'Problem' and 'New operation'
- Field of type 'Selection list' or 'Multiple values' to indicate to which internal party the release note applies
- etc.