Catchpoint from a QA perspective
Updated September 12, 2019

Catchpoint from a QA perspective

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

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).
It's hard to find the functionalities that I am looking for in the application. Even if I did something in the past, after a time I have to re-learn again where the functionalities are. This is a powerful tool, but not user-friendly. Texts in the buttons and menus are not always meaningful or easily comprehensible.
Every time that I have required help from the support team, I have had quick and clear answers. They have helped me until I'm satisfied, even if this took several days or even weeks. The support is excellent for both, simple (like finding an option or functionality), and more technical and suited to complicated questions (like fixing a script). They offer different levels of support and different ways to contact the support team through chat, email, phone and calling (where you can also share your screen if it's necessary).
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.
It's an excellent tool for monitoring results and looking for failures, errors, or abnormal behavior in your applications; also, you can configure alerts to be sent to the appropriate person in case of failures. It can be used to run a smoke test so you can save some time. It's not the appropriate tool to run regression testing.

Catchpoint Feature Ratings