Qyrus > Resources > Blogs > Feature Friday – How Test Repository Can Improve Your Testing Process

Feature Friday – How Test Repository Can Improve Your Testing Process

Summer has finally officially started! Although in some places, it certainly felt like it started some weeks ago, the Summer Solstice is finally here! Every day is now shorter from this point onwards, but that doesn’t mean that your outlook on test management should grow darker with the days. Qyrus has a fantastic test management solution and we have Punit Gupta, a Qyrus team member, here to discuss it in more detail with you! So, although the days are darkening, hopefully your outlook on test management will grow brighter! Without further delay, let’s jump in.

From a high level, provide a summary of Test Repository.

It’s is a very huge aspect of the entire test building experience of a user. In this feature the tests are stored in the repository and then can be reused across the different test suites either in Test Lab or Sprint.

The tests that are built in the repository are stored within the modules to which they relate. The tests that are created within the repository can then be imported into the test suites within the Test Lab or Sprint section.

The most interesting part about this feature is that the tests that are imported into the test suites can be updated/edited from the repository across all the test suites where the scripts have been imported to. This also works in reverse.  This helps increase the maintainability and the reusability aspects of building and maintaining the tests.

Another key feature of the repository is that the user has the option to save multiple different revisions of the script that the user is editing. They also have the ability to restore the tests to any of their previous versions that the user had earlier saved.

Describe in short what kind of use cases it specifically targets.

This feature specifically targets the maintainability and the reusability aspects of the tests that are built by the user. To explain this use case, let’s consider an example: suppose a user has built a login test and this is being used across multiple different test suites that are a part of the same Test Lab or Sprint cycle. If there is a change in the login flow where an additional step is added in the test, the locator changes, or the entire script needs to be changed, these changes can be updated across all the places where the script is being used. And again, this works in reverse, where the user can push changes back to the Test Repository. Finally, if a user wants to save the changed script without updating the old one, they can do that, also.

How is Qyrus’ test management different from how competitors have addressed test management?

Maintenance and reusability are key aspects of any test building experience and every competitor out there tries to solve this problem in their own respective ways. One way that our competitors typically address this problem is by making some aspect of their test like defining locators based on Page Object Model or defining a small block of steps as reusable by allowing the user to have them in one place and reusing them across other scripts.

Our approach to solving this problem is very unique when compared to the above-mentioned approach. While we have the same capabilities available on our platform in one form or another, the Test Repository makes the maintenance and reusability very easy and efficient as the users are not restricted to do the maintenance of their scripts in the repository alone but they have the options to edit/update the same in the imported suites and push back any updates to the repository and across other suites. This gives users more flexibility, adding to it is the ability to create multiple restore points of their script, allowing the user to make changes to the script and update them without having to worry about making mistakes as it can be restored at any point.

Test Repository was made with keeping testers and how they work in mind. It’s meant to enable testers to manage their tests in a better fashion. And, it doesn’t require any extra effort on the user’s end to set up or use. It’s an inherent part of the test building and testing process. The testers just create their test either manually or using our recorder and then add these tests as the part of the suites that these tests correspond to.

How does Test Repository make testing easier and faster?

Some of the concerns that testing teams have with respect to automation are building reusable components in their tests and the maintenance of these tests when things change. Qyrus addresses these key pain points of the testers with Test Repository, inherently making test management easier.

One of the most time-consuming tasks is maintenance of an automation script and making sure these changes are done and updated across all the other places as well. By using this specific feature in Qyrus, the testers will now only have to do the maintenance in the repository and push the changes to all the other places it is being used, making this cumbersome task easier and much faster.

In what way does it promote reusability, if at all? 

This feature can be best leveraged and is designed in a way that makes the testers build the tests in a much more reusable structure. The tests are built in the repository under different modules and allows the tester to design the tests in a much more reusable fashion, as these tests can be imported to multiple suites, multiple times.

Is there anything new we can expect to see out of Test Repository moving forward?

Speaking of the roadmap for this specific feature, this feature in itself has gone through multiple iterations to address different aspects of the test building experience. Having said that, the potential improvements that we are looking at is for it to be combined with the test data management, test orchestration, and test script management in its whole.

Well, what do you think? Test management never sounded so easy! Test Repository is built to enable the user to better manage their tests from one area to another. On top of that it gives the users the peace of mind that their tests are in multiple places and reusable across the entire platform. Well, let’s not keep you any longer. It’s summer, as we’ve said, and time to have some fun in the sun! We’ll catch you on next week’s Feature Friday.

app icon
Are You an Enterprise Client

Looking for a Custom Solution for Your Business?

Contact Us