...
A custom field is an additional property defined for Test assets. QMetry provides most of the standard fields define in Testing process; however, sometimes, the stakeholders wants to add custom fields to track the details at granular level. QMetry allows QA Managers to create custom fields for Test assets to customize the entities according to their set Testing Process.
...
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.
If you work in a highly controlled environment then it is likely that the version control is important. The Test cases in the library can be updated without affecting those which are already being run. (However, QMetry does not affect the executions until the user wants to sync the changes).
If you work in an environment where documentation and traceability aren’t so important then the version control may not be important; however, either way, it’s useful to trace the history and modifications to your test artefactsartifacts.
For example, as our airline website evolved, one more parameter is added on the login page along with username and password. So the Tester has created a new version of a Test case with an added step instead of updating the original one.
...
Verify customer login
Verify Employee login
Verify corporate login
In these 3 scenarios, the Test case is the same but requires different data. QMetry allows testers to create a set of Data with different combination combinations via the Parameter feature.
Test Planning
A Test plan serves as a road map to the testing process that has all the necessary details related to execution coverage. It allows the QA manager to accurately estimate the required effort and cost to execute the testing process.
...
Test execution is a key phase in Software Test Lifecycle. It refers to the execution of test cases or test plan to ensure the fulfilment fulfillment of the pre-defined requirements of the product. It involves the execution of the test and comparison of expected and actual results.
...
Test varied and concise reports of QMetry allows us to evaluate the current status of project and quality of the product, track manual and automation testing efforts, Traceability between Requirements and Test assets etc. Using these reports a QA manager can take corrective actions if necessary.
...
The API is designed to directly upload the Test execution in QMetry. If you are using any of the following QMetry supported Automation frameworks then you can upload your execution results in QMetry using QMetry Automation.
Reusability
As said above that QMetry strongly supports re-usability, how it can be an exception for automation? Automated Test cases are reused based on their Summary, Description and Steps. Find a detailed description of how reusability works for different frameworks here.
Automation Reports
QMetry provides multiple reports for automation.
...
Open API
The QMetry Open API supports almost all the operations that can be done manually on QMetry UI.
...
The different projects/products/software have different components, labels, priorities, environments, Execution results, workflow statuses, custom fields, etc.
Add components, labels, priorities, environments, Execution results, custom fields that suites suit your product.
Add parameters for Test cases to Test a test the same scenario for varius combination various combinations of data sets.
Enable the feature - Auto-update execution result to update the test case execution result automatically in accordance with the change in test step execution result.
For quick access of execution status on execution screen set the preferred execution statuses.
Add custom status for Test Cycle, Test Plan to match with your sprint workflow. Not all organizations manage status for Test cases as they are meant to be reused. Test cases can have different statuses like Draft, Reviewed, Approved etc.
...
The permissions restrict the unwanted use of QMetry. If the permissions are not enabled, every user can perform every operation. QMetry recommends that the permissions should atleast be enabled for Modify Configuration, Deleting assets.
...
Once QMetry is installed or any new project is created, to enable QMetry features in that project, a Project admin has to enable QMetry app in case the team wants to use QMetry in that project.
...
A Project admin can decide the issue type of Jira that should be considered as a Story or a Bug. Generally, all your requirement issue types such as Story, Epic, Task should be considered as Story and defect issue type types such as Bug should be considered as Bug. Other than Jira custom issue types, custom issue types can also be enabled as Story or Bug.
...