We use it for test case management. We used it to define valid and invalid inputs and to create tests for both scenarios. This involved manual testing, such as boundary value analysis and exceeding valid ranges.
Helped with agile testing, provides exploratory testing and screen capture capabilities but visibility of test cases could be improved
What is our primary use case?
How has it helped my organization?
It definitely helped with agile testing. We used to give the development team test cases in advance so they could validate their implementations against the test cases. This helped because the developers had the test cases beforehand.
What is most valuable?
QMetry has different aspects. It provides exploratory testing and screen capture capabilities while running tests. It has a recorder integrated. If you run a test on an application, it will record every aspect of it.
For example, if you execute a user scenario, it will record what the user does within the application and generate a script. This can also be used for quick automation.
Moreover, if we have an automation framework, QMetry can integrate with it.
QMetry can also handle load testing in web-based applications.
We have integrated it with a bug-tracking system, but not for automation. It was not difficult to integrate it. This integration was mainly for reporting purposes, such as creating reports directly from QMetry.
What needs improvement?
QMetry team upgrade features based on the number of users experiencing certain problems. If fewer users encounter an issue, they may not address it. They have a different concept where feature development depends on the frequency of user interaction.
For me, the visibility could be improved. When executing a test case, you needed to open it separately to read the steps. I'm not sure how it is now, but previously the visibility of test cases wasn't great.
For how long have I used the solution?
I've been in testing for 17 years. So, I have worked with this product for quite a long time.
How are customer service and support?
The team provided support for integration, but new feature enhancements take time.
There is room for improvement in the customer support. Xray has better support.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
For management, we used tools like QMetry and Xray for test management. There were other product-dependent tools that required script lists to automate certain tests.
I have also used JFrog Xray. Xray is much easier to use and gives better visibility.
How was the initial setup?
There was one difficulty while implementation, but it wasn't due to QMetry. If you're using a tool for the first time, it's usually easily implemented.
We used QMetry and then moved to JFrog Xray, which was difficult.
Migration is difficult because we used to attach our data directly to Jira tickets. We migrated successfully, but we had to recreate links for all test kits. It's difficult to migrate within the same project if you have attachments in the previous tests.
What was our ROI?
The best benefit was for new hires. We used to write our test cases in simple English within QMetry, so anyone who knew English could understand them. This helped with training new hires.
It helped us save time. Instead of manually instructing new hires, having well-written scripts in QMetry that anyone could understand saved time in training and ensured everyone could comprehend the test cases. It saved time at various levels, not just daily. It saved about two months out of five years.
What's my experience with pricing, setup cost, and licensing?
QMetry was cheaper than Xray, which was based on the number of users. It was around $10d per user, while QMetry was closer to $4 per user. So it's about half the price.
What other advice do I have?
I would recommend Xray. So, JFrog Xray.
Overall, I would rate the solution a seven out of ten.
