I really appreciate how QuerySurge facilitates the easy comparison of table data based on query pairs, allowing me to identify differences across various scenarios with efficiency. The ability to store scenarios that can be reused with different data connections is incredibly valuable for our regression suites, as it streamlines the process of running QA tests for each release. Once set up, I can effortlessly trigger these scenarios using specific database connections and have the results ready for review within just 10-20 minutes. Additionally, the capability to export the analysis into Excel is a major advantage, as it enables sharing detailed results with colleagues who might require a deeper dive into the data. Furthermore, the integration with Jenkins script for automating scenario triggers ensures flexible and time-efficient operations, especially for after-hours testing. Although I wasn't part of the initial setup team, my experience with updating QuerySurge to a new version was smooth, indicating the software is user-friendly in terms of maintenance and updates. Review collected by and hosted on G2.com.
Sometimes the analysis in QuerySurge creates false failures, such as when only one column in the table data is different, but multiple columns are highlighted as differences. This leads to confusion and false alerts. Additionally, when data are exactly the same and should match perfectly, they are occasionally incorrectly highlighted as discrepancies. This requires testers to manually scan rows or export data to Excel to apply formulas and verify that no true differences are being overlooked. Review collected by and hosted on G2.com.
Bruce,
Thank you for the detailed review and for outlining how QuerySurge supports your QA process. It is great to hear that reusable scenarios, fast execution, Excel exports, and Jenkins integration have made your regression testing more efficient. We’re also glad your upgrade experience was smooth, even though you weren't part of the original setup.
Your feedback on false failures is important, and we appreciate you calling it out. We continue to refine how QuerySurge surfaces differences, and your examples help us target where improvements are needed. Ensuring clear, accurate comparisons is a priority, and reviews like yours guide that work.
Thank you again for taking the time to share your experience and for relying on QuerySurge to support your testing workflows.
Regards,
Bill Hayduk
CEO
