Review the email rules
Go through the list of e-mail rules. However, bear in mind that the current settings work for most ReQtest users.
Is a template text needed for any of the fields? One example is that if the requirements are in the form of user stories, then you can apply a template that looks like this: “As a <role> I want to be able to <task> so that I <goal>”. This makes it easier for users to remember all the parts of the user story.
For bug reports, you can apply template text in the error description field, such as: the customer’s personal identification number, test data, browser version or other information that the testers sometimes forget to add to the bug report.
Grouped dropdown lists
You can create groups of values in drop-down lists. This is very convenient for dropdown lists with many values, since it makes it much easier to use them.
Examples of how such a list of subsystems might look like:
- New York
To create such a list, simply type -> after the group name. Example: Inventory -> Hamburg.
Are there any of the fields that you wish to clarify to your users? In that case, you can add an explanation text. This is displayed to users when they hover over the question mark next to the field.
Share fields between forms
It is possible to share fields between ReQtest modules. If you change the field contents in one of the modules, then that change is reflected in the other modules. Subsystem is a field that already is shared between modules. Other fields can be shared, such as priority or fields like probability and consequences that can be used for risk-based testing.
Add fields if needed
Are there any metrics that you want to follow up continuously using ReQtest? To make this easier you could considering adding more fields specifically for the metrics you want to keep track of.
This concludes our five-article series about customising fields in ReQtest.