Note: this is not paid promotion, just personal experience on how we choose our Test Case Tool.
When Testera was founded there was an idea to adopt all the tools our clients were using totally. But then after some time and gained experience we saw that most of the clients who do not have a testing department at all would not have tested too also (obviously). Then the challenge arrived, what test case tool to choose to fit all various projects, starting from the NFT marketplace to the payment aggregator system to the artistic talent sharing platform. Anyway, our suggestion is to have a clear goal, what you want, because the marketing of providers can bluer your main motive why you want to have. So this is maybe not what you want but our motives were:
To meet a budget of 1-2 K per year
To be simple to onboard, like minutes - hours
To Have steps inside the test case
To have simple reports
But first of all how to find any starting point and then make a benchmark, well, we started by simply googling all tools we know and typing keywords: an alternative to or something like that. At the very beginning all Jira plugins were not a good fit for us, because we will not know do our clients use Jira, and if not.
So what to do next, some blogs provided a good starting point, also later, we used sites for alternatives and comparison
So what tools we took into consideration:
TestRail (we used it before and it is well known)
PractiTest (also good marketing)
TestMonitor (simple solution)
Test Case Lab
TestPad (the simplest solution that exists)
Testiny
Here is the comparison table with what we needed
Provider / requrement | 1000$/Year budget | Simple Onboarding | To have steps inside TC | Simple report |
Test Rail | ➖ | ➖ | ➕ | ➕ |
PractiTest | ➖ | ➖ | ➖ | ➕ |
Test Case Lab | ➕ | ➕ | ➕ | ➕ |
TestPad | ➕ | ➕ | ➖ | ➕ |
TestMonitor | ➕ | ➕ | ➖ | ➕ |
In the end, as you see we picked Test Case Lab, there are for sure some things that we do not like, but, for now, it is covering our needs 80%.