Catchpoint from a QA perspective
Updated September 12, 2019
Catchpoint from a QA perspective
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Catchpoint
The QA team uses Catchpoint to monitor our company's site. We have jobs running all the time, but we also run the tests on Catchpoint before and after every release and every deploy. It helps us check for the sanity of our site and systems in a quick and effective way.
- It's a powerful tool.
- It has many useful functionalities.
- It has support for different kinds of tests.
- It has an excellent support team.
- They could provide better technical training material.
- The interface is not user-friendly.
- It's very helpful to run tests after a deployment or release, so we can quickly see at the results before investing time on testing manually or running other tools.
- It provides alerts, so we can be aware of errors even during the weekends (when our engineering team is not usually looking at the application).
We still use other tools, but with different purposes. Catchpoint is running over our production environments and provide alerts in case of failures. With HipTest we run regressions and manage test suites for both, manual and automated regressions also is integrated with JIRA, which is good because we can link the JIRA tickets/stories with the test scenarios in HipTest. Jenkins is used (for us) in the same way as Catchoint, and it is a tool that we are going to stop using in the future because maintaining scripts is easier in Catchpoint than in Jenkins.