QMetry Test Management provides different ways to reuse test assets to reduce maintenance, increase efficiency and productivity of testers. You can use the following tips and techniques to reuse based on your testing processes.
Versioning Test cases
You already have a test case with steps to validate a scenario. To incorporate future improvements for the same scenario a tester may want to reuse an existing test case and just add/edit/delete/reorder steps. QMetry allows testers to version a test case with detailed audit logs preserving the executions done against the previous versions. You can reuse the same/different versions of test cases in multiple test suites for reusability.
Copying Test cases
Often testers need to validate a scenario for which most of the steps match with an existing test case in the same or different project. They can do this by copying a test case with a new key, modifying the existing steps and jumpstart the validation. QMetry allows creating the exact copy of a test case with a new key, in the same project or another project.
Shared Test cases (steps)
There are different validations in a project that share some common steps. So, instead of authoring the common test steps in all the validations, testers can create a shareable test case. QMetry allows testers to create shareable test cases, manage them independently and reuse these shareable test cases as steps into other test cases. This prevents authoring of repeated test steps and helps to increase productivity by saving time and maintaining consistency. Whenever there is a change in the shared test case, it simply needs to be modified in the shareable ‘master’ test case and all the impacted scenarios will be auto covered.
Test Data Parameterization
At times, there are validations that are performed with different set of data but the steps are same. Testers can avoid the rework required to create different versions/test cases for such scenarios. QMetry provides Test Data Parameterization feature that allows testers to execute same test case multiple times with different data input. This feature replaces the traditional practice of entering hard-coded input values and creating duplicate test cases. Instead, the variables are entered as parameters in the test steps. Testers can create simple to complex data grid values using multiple parameter combinations. During execution, the parameters are replaced with actual values and testers view test cases for different combinations and execute them with different statues.
Sharing same test cases across multiple projects
QA teams often execute the exact same set of test cases for multiple customer deployments, projects, sites, clients or product editions and keep execution results separate. Such teams manage their test cases in a central library space and then clone the library/or set of test cases to the new space for their new site/clients’ fresh executions.
Although QMetry allows cloning of projects and copying the set of test cases for such teams; this approach creates a new key or copy of test cases. Based on our experience we find that this becomes a problem to manage Library test cases and new project test cases as they go out of sync with version or changes. Also, executive management/stakeholders do not get proper cross project reports.
That’s why it’s not an ideal way to incorporate reusability. To avoid these situations and prevent customers from creating new copies of same test cases in multiple projects, QMetry allows sharing of test cases across projects. The test cases from library project are linked to multiple test suites of other projects. Also, different versions of test cases can be linked to multiple other project test suites. Here, the test case copy, id and key remain the same. It is only the executions that are stored separately. Stakeholders can see the details of all executions across projects in the library test case itself – a single place. QMetry also provides cross project reporting to get dashboards, graphs, statistics of multiple projects together.
Synchronizing test cases across projects by creating new copies
This feature is for organizations that execute the same set of test cases on multiple projects, clients or vendors with permission-based or restricted access for their users. The organization maintains multiple projects for its testing activity. Users can access the data only for their own project and do not have access to other projects/clients/vendors data OR even all assets of library/repo projects due to proprietary compliances.
The parent company of such QA teams manages their test cases in a central library or repository project. Test cases from the repository are repeatedly used in these different projects. When a user with access to repository/library project wants to share the test cases with other projects, the test cases are shared as child Test Case. The shared child test cases are created in the destination projects with a new key, but they are read only and can’t be edited. These child test cases are linked to their parent test cases in the library projects. The parent company has the ultimate right to select the set of test cases and just push specific versions of them to required projects. The users of destination projects have the rights to sync or pull the incremental changes as and when needed.
Similarly, the user of parent repository project has the rights to push or sync test cases to destination projects, so they do not miss any important update. The source project test case is identified as a “Parent” and the destination project in which the test case is copied is identified as a “Child”. All associated child test cases can be viewed from the parent test case and the same way parent test case can be identified from child test case. Stakeholders can see details of all executions across projects in the library test case itself – from a single repository. QMetry also provides cross project reporting to get dashboards, graphs, statistics of multiple projects together.
Reusing the same test suite for multiple Release/Sprints, Platform/Environment
Test suites are a group of test cases that are executed in a logical sequence to validate end-to-end user scenarios. QA teams reuse the same scope (or increased) of test cases for repetitive testing against different builds in multiple releases and sprints for different combinations of platforms. For example – regression suites need to be re-executed with every release and sprint. QMetry allows teams to re-use the existing test suites with multiple release/cycle and platforms to re-test the test cases and reduce the effort in creating test suite for each release/cycle, platform combination.
Copy a test suite with multiple options
There are times when QA teams need to re-execute the same test suite again as a fresh execution or a selected combination of test cases like the failed ones from the original test suite, but still want to keep a copy of previous executions. QMetry allows copying of a test suite with multiple options such as – copying test cases with selected Execution Status or copying test suite for a platform, release and cycles combination or copying test suite with the latest version of all the linked test cases.
Reusability helps save time and effort involved in repetitive tasks of test creation and execution. In today’s agile and fast-paced landscape, teams must find smarter ways of testing, reusing existing test assets and minimizing rework. Not only does it enable testers to focus on more creative and exploratory side of testing. But it also helps reduce the total cost of quality and maximizes return on investment.