What problems is TestMonitor solving and how is that benefiting you?
Here at Iris we have 9 different software products that go through internal User Acceptance Testing for each release before being rolled out to our clients. Before TestMonitor, at best we tracked test cases in spreadsheets that were passed around via email, and at worst we relied on users going through test cases in their heads and randomly checking the product. Now with TestMonitor, we have fully defined Test Runs with hundreds (sometimes thousands) of Test Cases that are assigned to the UAT team members who can purposefully go through each one, giving it a pass/fail grade and (if failed) create issues that are immediately turned into Jira tickets (via the Atlassian integration) and assigned to the Development team. They, in turn, can resolve the issue and send the test cases back to retest, which alerts the tester via Teams and email that the issue is fixed and they can retest (and hopefully pass) the test case. It provides accountability for all the testers and developers, and a series of beautiful dashboards that our executive team can get a quick look at progress on the Test Runs and a snapshot of the issue resolution progress. It gives us a series of test suites for all of our products that can be called upon again and again as we roll out new releases and new features. Review collected by and hosted on G2.com.