The perfect tool for test management and defect life-cycle
Overall Satisfaction with Tricentis qTest
- We use qTest for test management such as creating manual and automation test cases, executing it on qTest and updating the test case status.
- We also use qTest to raise defect or bug.
- While we have integreted qTest with TOSCA , we are triggering DEX execution from qTest itself and monitoring the test case status, which is helpful during E2E testing.
- qTest has the feature to link test cases to tosca automation cases , that we use for jenkin jobs and parallel execution of test cases.
- In our organization we have integrated qTest with ADO board, so that we can have realtime tracking of defect, test case and story completion.
- Creating requirements which are getting pulled from ADO board as a part of testable stories and linking test cases to have track of the story and related cases from requirements itself.
Pros
- Test case management.
- Raising defect or bug is very easy and hassle free. We can track the status on the go
- It has recycle bin for recovering your mistakenly deleted cases.
Cons
- In requirements , we can't add multiple test cases at once, or search multiple cases at once, need to do one by one. Here actually qtest needs to improve.
- Linking cloud hosted qtest and on-premise TOSCA is very difficult especially when you are working with client system with security wall. It requires tunnelling software which is not recommended.
- Test case and requirements analysis becomes easier when you will get all test management needs in one place.
- connecting ADO,QTEST,TOSCA together helps to monitor test results and test quality on the GO
- Defect life-cycle is easier to maintain so as to ensuring a defect free system.
- ngRok tunnelling software
- Selenium-tried but still working on it.
- Jenkins
- Docker
- Azure Board
- Tricentis needs to comeup with better solution rather using ngrok for tunnelling and connecting on-premise TOSCA with cloud qTest.
- The Jira integration is quite easy as well as ADO(Azure Board).
- Tried integrating the Selenium scripts but still trying.
- For connecting qTest with tosca requires lots of tools at a time like tunnelling software like ngrok, tosca server, DEX , etc . which is really not handy.
- In depth control and monitoring over test cases, while we can create manual and automated cases on the fly.
- The folder structure helps to manage the test cases very efficient way such as modules>> test cases>> test runs>> test suite.
- The defect lifecycle can also be maintained , while screen shots as evidence can be added to the test execution and defects for reference.
- Rapid testing in case of E2E while connected to test automation TOSCA cases with jenkins and DEX execution activated.
I have worked on Jira, but i found it more difficult interface to handle. It was not user friendly. The defect management was also not impressive. qTest experience actually helped me to take decision while evaluating.
Do you think Tricentis qTest delivers good value for the price?
Yes
Are you happy with Tricentis qTest's feature set?
Yes
Did Tricentis qTest live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Tricentis qTest go as expected?
Yes
Would you buy Tricentis qTest again?
Yes
Comments
Please log in to join the conversation