Best Software for 2025 is now live!
Show rating breakdown
Save to My Lists
Claimed
Claimed

Top Rated Testpad Alternatives

13 Testpad Reviews

4.0 out of 5
The next elements are filters and will change the displayed results once they are selected.
Search reviews
Popular Mentions
The next elements are radio elements and sort the displayed results by the item selected and will update the results displayed.
Hide FiltersMore Filters
The next elements are filters and will change the displayed results once they are selected.
The next elements are filters and will change the displayed results once they are selected.
13 Testpad Reviews
4.0 out of 5
13 Testpad Reviews
4.0 out of 5

Testpad Pros and Cons

How are these determined?Information
Pros and Cons are compiled from review feedback and grouped into themes to provide an easy-to-understand summary of user reviews.
Pros
Cons

Overall Review Sentiment for TestpadQuestion

Time to Implement
<1 day
>12 months
Return on Investment
<6 months
48+ months
Ease of Setup
0 (Difficult)
10 (Easy)
Log In
Want to see more insights from verified reviewers?
Log in to view review sentiment.
G2 reviews are authentic and verified.
Verified User in Information Services
UI
Mid-Market(51-1000 emp.)
More Options
Validated Reviewer
Verified Current User
Review source: Organic
(Original )Information
What do you like best about Testpad?

It's a good tool for manual testing. Tests can be written very easily and it makes it very easy to pass tests on to other, even non-technical, coworkers so that they can complete them too. Great for testing new features, Bugs and especially regression-testing. Test reports can also be shared publicly, so there's no need to create accounts for customers to be able to see the tests results.

One of the most useful features is the ability to tag test steps to only make them available for specific test runs, eg making certain steps only available to test runs for mobile devices. Review collected by and hosted on G2.com.

What do you dislike about Testpad?

Unfortunately the interface gets in the way more often than not. The developers insist on overwriting your browser's right-click function, which is something I strongly dislike in Webapps. If a Webapp runs in a browser, it should allow native browser functionality. It feels very strongly as if they wanted to write a Desktop App, but had to settle for a Webapp instead.

Lots of small things are way more difficult/cumbersome than they should be, such as editing test steps after completing a testrun (eg adding comments to explain the problem) requires you to first change the testrun's status to "In Progress" (the bar you need to click on to do so is very flashy, but simultaneously confusing and not user friendly at all). When editing a test step in a completed run you have to be careful to press escape instead of the big green and Red Pass and Fail buttons, otherwise it changes your testrun's status back to "completed", which is an annoyance when you want to edit multiple test steps. Or having to manually uncheck "Inherit Test Results" when starting a new test run (this should really be opt-in by default, not opt-out).

These things sound like small annoyances, but many such small annoyances lead to a very counter-intuitive interface. For a tool that should be very simple, we lose way too much time trying to explain to new employees how to work with it. I still get confused with its interface from time to time, and I've been using it for more than a year.

Had it been up to me, I would not use this tool. I find the user interface one of the most infuriating I have to work with on a regular basis. I strongly recommend that the developers reconsider their interface in terms of simplicity and predictability. Good user interface design is one of the most important things to keep in mind when designing a tool like this and I feel like that didn't get nearly enough attention during the development of Testpad. This is exactly why designing according to KISS principles is so important. Review collected by and hosted on G2.com.

Katie F.
KF
Groundfish Data Services Manager
Environmental Services
Mid-Market(51-1000 emp.)
More Options
Validated Reviewer
Verified Current User
Review source: Organic
Business partner of the seller or seller's competitor, not included in G2 scores.
What do you like best about Testpad?

Quick and easy to start using, and helps me ensure that my 50th round of testing is just as detailed as my 5th. Review collected by and hosted on G2.com.

What do you dislike about Testpad?

I have no complaints about this app and feel confident asking my team to use it. Review collected by and hosted on G2.com.

Verified User in Medical Devices
AM
Small-Business(50 or fewer emp.)
More Options
Validated Reviewer
Verified Current User
Review source: G2 invite
Incentivized Review
What do you like best about Testpad?

easy to use; easy to navigate but there are enough options to organize the test scripts; there are plenty of places to put in comments regarding test script/ test results Review collected by and hosted on G2.com.

What do you dislike about Testpad?

The test needs to be structured to be a either a definite positive or negative, so each 'test' needs to be worded pretty specific. It's good for regression checklist but if a new bug comes up there's not a great way to indicate it. Review collected by and hosted on G2.com.

Response from Stefan Butlin of Testpad

Thank you very much for reviewing Testpad and very pleased to hear you like the ease of use. If you would like to make any specific suggestions for improvements, please don't hesitate to write to me on stef@ontestpad.com, I'm always keen to understand what you're trying to do and how Testpad can make that easier.

For the benefit of other readers I would like to emphasise the flexibility of test structure as it would be a shame to get the impression Testpad is only good for regression testing.

Results are indeed collected as 'pass' or 'fail' (unless queried, blocked or skipped), but it's up to you how literally you take this. For example, an Exploratory test plan (the polar opposite of regression testing?) might just say "login functionality" and a "pass" here would mean no problems found. Or sub-headings under a title of "login functionality" could include items like "unicode characters", "blank fields", "forgotten password"... all non-specific but a "pass" can still mean "no problems found", and leaving you with a nice summary of the areas you looked at.

If you do find a new problem, you can raise it in an issue tracker like Jira and leave a link to it in Testpad, or you can include a comment in Testpad, or... you can even add new test rows right there and then during testing to a) document the new ideas and b) so you get reminded to cover it again next time.

Lastly, Testpad gets used on projects big and small. The largest to date has been on a $multi-million console game with over 100 testers!

Please don't hesitate to write in (stef@ontestpad.com) if you'd like help with, or just to discuss, any of these ideas. As I said, I'm always keen to understand how you're working and how Testpad can make your testing more productive.

Best regards, and thanks again for leaving a review

Stefan

(Founder, Testpad)