testRigor Answer Your Questions

How does your tool improve my life as someone in QA?

testRigor allows manual QA to create robust automated test cases with plain English statements.  The approach allows non-technical manual testers to become sophisticated automation testers with no knowledge of coding.  

Additionally, testRigor created test cases are 99.5% maintenance free allowing you to create more test case coverage rather than maintaining broken tests.  This allows a manual QA professional to focus on creating meaningful tests while executing more tests in less time.


What misconceptions are there around your tool?

The misconceptions are that automation tools replace manual QA testers are expensive and difficult to create stable meaningful tests.

testRigor was built from the manual tester perspective since they are the people who use the software internally the most.  testRigor is not a replacement for manual QA however an augmentation that allows manual QA to create their tests while removing the repetitive time consuming parts of regression that are prone to human error.  

Additionally, when testRigor’s costs are compared to an automation engineers salary and the costs of adding manual testers, the testRigor system works out to be much more affordable in the long run.  The amount of tests you can execute and the time you will save are huge factors.  

testRigor allows manual testers to capture the tests they would execute manually and turn them into automated tests with a few tweaks with plain English statements.

What tool feature are you most proud of?

The ability to test complex application features without knowing the underlying code structure is a key feature.  testRigors approach takes the view of the manual tester and how they perceive the application to be tested.  It is not tightly bound to the code implementation.  This allows testRigor tests to remain stable when a software system changes its underlying platform or has a major refactoring of the code.  If the business rules of the application under test stay the same, so do testRigor tests.  

In other test systems making significant code changes will break entire test suites rendering them unusable.  With testRigor there is a simple copy replace functionality that can be used to seamlessly update any breaks from code changes.


What is your roadmap and how do you decide what to prioritize?

Our roadmap is constantly evolving based on market demand.  We are in tune with breaking industry movers such as hyper automation and citizen engineers while gearing our tools for the dynamic market.  Key roadmap drivers are to keep allowing manual QA to build automated tests, continue being the best at solving the test maintenance problem and improving our plain English test system so it may fit in the bigger picture of process automation. 


How do you involve your customers in your tool development process?

Every customer we have has a personalized relationship with our CEO down to our customer service team.  We are in constant contact asking about required features, issues that need to be addressed and how we can better serve them.  

After they have time working with the testRigor tool, we interview them with a set of questions that allow us to gather metrics on their internal testing improvements for time, value and expense.  We take their feedback and feature requests and analyze their impact on our development and their gain as a customer.


How do you test your own tool?

We test testRigor with testRigor.  In addition to other testing methods,  we are able to test testRigor with our own system since it is web based.  This is not the only testing we do but we use our own tool internally on our own products and systems.

What is the most under-appreciated feature of your tool?

Reusable Rules are the most under-appreciated feature.  We allow our test cases or test case steps to be saved as a reusable rule.  So instead of typing the same steps over and over, you can create a modular rule that you can write instead, saving time in typing and keeping consistent with how you always execute the same repetitive steps.  We spend time educating our users on how reusable rules will improve their test case writing.

How do you support your customers when releasing tool updates?

We provide weekly release notes to our customers.  Additionally, we have a customer support team that is in constant contact with them to answer any questions or guide them through new features.


What type of support is given when purchasing your tool?

We create a direct line of communication with all of our customers via joint Slack or MS Teams channels.  In addition, we create Zendesk accounts for our customers so they can report bugs and make feature requests.  Furthermore, we provide 9 calendly links for different types of meetings they can schedule at any time.


How would you like to keep the conversation going with the Ministry of Testing community in the long term?

As a next generation testing tool geared towards driving manual QA to automation testing, we hope to showcase our product individuality on Ministry of Testing.  As a quality driven company, we want to build the best practices on how and what to test with our system so manual QA can transition to automation.  We would like to present webinars, build content and build community awareness of our product and how it fits in today's testing environment.