...
“Validate that a flyer is able to log in” test case already exists for Story 3 above. We can reuse the same test case for Story 4 below.
...
Reusing test assets in the event of repetitive user actions, save human efforts, and keeps test artifacts in-sync across the test documentation.
...
For example, let's simply group our FlyHigh project test cases feature-wise.
...
Using Custom fields
A custom field is an additional property defined for Test assets. QMetry provides most of the standard fields define in the Testing process; however, sometimes, the stakeholders want to add custom fields to track the details at a granular level. QMetry allows QA Managers to create custom fields for Test assets to customize the entities according to their set Testing Process.
For example, In the test case, the QA manager wants to track the Feature and URL of a website.
...
Version controlling
QMetry offers a strong reusability concept by allowing users to create a new version of the Test Case instead of updating it. Let’s see how version control of Test cases is important.
...
Execution Summary by Environment
...
Execution effort summary
...
Traceability
...
Consider all possible scenarios while constructing an automation script for automated test cases. Well-written manual test cases provide a strong base for automation. It also helps Automation engineers write quality code and streamline automation scripts with manual test cases.
...
Automation API/Maven/Jenkins
...