Should you be joining in?
Testpad has been made for...
Testers in startups
It's all too easy for a startup to short-change software testing under the pressure of tight deadlines. Testpad's speed of editing means more tests can be planned and run in whatever time is available. Testpad's checklist approach is easy to adapt to your style of software testing; whether it's just listing the names of 10 important features, or recording your 50 favourite last minute checks, or going all the way with hundreds of tests to work through.
With a free Starter plan, easy data import/export, and short learning curves, it's a low-risk investment to give it a try for your next release.
Professional Testers in established SMEs
Testpad isn't just another test-case management tool. You should check it out if you've been looking for a better software testing tool for years, have opted for something that's OK but no-one on the team likes much, and/or still have lots of scripts in spreadsheets.
Testpad's checklist approach and keyboard-driven outline editor make it really fast to write, re-write and re-organise test scripts in minutes. Styling tests as checklists gives you great freedom to structure scripts with as much or as little detail as suits the product. You might use a short script as the charter for some session-based exploratory testing, or a longer script as a more detailed scripted test.
Testpad comes with a free starter plan and monthly subscriptions can be canceled at any time. So with easy data import and export if you want out, why not pick a guinea pig of an upcoming release to give it a try with one of your teams?
Software engineers who do the testing themselves
Testpad's simple checklist-style of test planning makes it very approachable for non-testers and testers alike. How complicated can a list of things to check be? Exactly. Testpad lets you plan as much or as little as you need. Its keyboard-driven editor means you can rattle off hundreds of test cases without even touching the mouse.
Then add the ability to run tests from a mobile or tablet and you've got a very cool way to run through your scripts with minimal context switching every time you want to pass a test or read the next step.
Testers in an agile development process
The word 'agile' can imply many things these days, but at their core, most agile processes involve the idea of developing a product through a series of iterations (commonly called sprints). The rapid iteration of what the product is and does puts a unique burden on how to test it, especially when trying to document those tests and not just wing it with adhoc testing each release.
Testpad doesn't solve these problems straight out, but it gives you a flexible and convenient tool with which to maintain as many or as few test scripts as suits the sprint. You might simply build a script with tests taken directly from the user stories for the current sprint, or you might start with those and flesh each with as much detail as time allows. From sprint to sprint, you can simply extend your growing script, or make a copy and edit anew. The advantage of the latter being you can archive the tests and results as they were at the time, whilst keeping your current version up to date with the product - no more editing cases and making them out-of-date with results recorded in previous test runs.
Simple User Acceptance Testing
Testpad's straight-forward approach also makes it suitable for simple user acceptance testing. Just build out a structured checklist of the features, user-stories, or capabilities you want to prove, and then run through them on each release to the client. Testpad's reporting makes what was and wasn't tested very transparent; it's simple to scan the list of test cases and get a feel for the scope and quality of the testing.
Further, just the use of proper tool in the first place will look much more professional than a zip-file of spreadsheets. Why not give it a try on your next deliverable? It's easy to copy and paste existing specs in, and similarly simple to get your data out if you decide Testpad is not for you.
Testpad is less suited to...
Testpad has been built with smaller teams in mind as it simply doesn't have enterprise-sized features or integration options for other enterprise tools. However, despite this stance, it seems many testers we've talked to within bigger organisations share similar stories about their dissatisfaction with the current tools and have also resorted to spreadsheets or wikis.
If this is you, then please get in touch (firstname.lastname@example.org). Maybe you can try Testpad on a side project with just a small group?
Teams happy with traditional QA tools
If you like your formal software test cases, complete with steps to execute, expected outcomes, environment, priorities, and other meta-data, then Testpad isn't for you. You'll find the checklist/outline structure too free-form and flexible.
Teams looking for solutions that integrate requirements and issue tracking
Testpad doesn't track dependencies between requirements documents and test plans, nor is it an issue tracker. Testpad does, however, let you link a test result with an issue in an external tool, and you're always free to include a reference to a requirement ID in the text of a test. It's just this isn't what we designed Testpad to be good at, and there are existing (and more expensive) tools on the market if that's what you need.