Images
Testpad is a beautifully simple test case management tool that reinvents manual testing with an efficient checklist approach. More convenient than spreadsheets. More agile than heavyweight case management. Spend less time writing, more time actually testing.
Customer Reviews
User in Information Services
Advanced user of TestPadIt'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.
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.
Think carefully about who is going to use Testpad and what their needs are. In smaller teams, Excel or Google sheets might accomplish everything you need from a tool like Testpad. If you're going to have a lot of customers or non-technical users run tests in Testpad, the unnecessary complexity of the interface might get in your way when you have to explain everything to them every time.
It gives us a centrally-available manual testing repository that can be made available to the entire team to either view, edit or run. It allows allows us to send easy-to-interpret test reports to our customers so they can see exactly what we tested and what the results were.
