Feedback

Frequently asked questions

How I do attach a screenshot or image to a test case?

Use Drag'n'Drop onto either the Test Details dialog or the Test Run dialog. Uploaded images can be previewed with the built-in preview window, including during testing, or downloaded for viewing in external tools.

Where is the automated testing?

Testpad is about manual/hand testing for all the tests that you cannot automate. It's a tool to help you write test specs, or checklists, and then run through those specs, manually passing or failing each test as you go.

Is there an API?

Not yet, but watch this space... (and email stef@ontestpad.com to voice your enthusiasm if you'd like one).

How can I backup my data?

Use the Account Settings link towards the bottom left of the Project view, go to the Backups Tab, and use the link provided to make a ZIP file of all your data. This isn't suitable for re-importing, but is perfect for peace of mind that you have your own copy of all the data that's in Testpad.

Note that Testpad is already backing up all data with hourly snapshots of the entire database, but this is for system-wide disaster recovery, so we understand if you'd like your own copies too.

How do I save my changes?

Testpad saves changes as you go. For test descriptions, this happens when you move focus off the current row (or press Escape to de-focus it). For test results, it happens as you click pass or fail. You can always experiment to test it: just reload the page to see what's on the server.

When editing test cases, the saved/unsaved status is shown in the top left-hand corner. Further, if you try to close the browser, or navigate off the script editing page whilst there are unsaved changes, Testpad will prompt you before losing that unsaved data.

What's the difference between a "retest" and a new test run?

You can use test runs however you like, but the difference between a retest and a new test run is in how progress percentages are calculated. Each new test run is included in the progress. However, retest test runs replace the run that they are a retest of. In this way, you can retest a previous test run and have the progress bar reflect the updated test results.

Use retesting for new builds that are part of the same release. Use whole new scripts (or folders of scripts) for new releases.

How do I run through the tests again on a new build, without the progress bar including the first run?

See the previous question! When a test run is completed, click on 'start a retest' in the Run Details Dialog. This prepares a new test run that is a replacement (a retest of) the previous test run. Old test runs like this are then not included in the progress bar.

How do I make a new first row in a script?

Click on the existing top row and press Shift-Enter. This makes a new row above the current row.

Or the complicated way: click on the first row to focus it, press Enter to make a new row after it, and then press Ctrl-UpArrow to nudge the new second row into first place.

Where do I put the expected results for a test?

Testpad doesn't draw a distinction between documenting the steps to execute a test case and the expected results of each step. You are free to use the test row (and the extra notes box via Alt-M) however you like.

In some situations, the expected result is obvious from the wording of the test case. Where it's not, you can either append some more text to make it clear, or you can add notes to the notes box.

Access the notes box by pressing Alt-M on a case, or doubling clicking on it's ID number on the left, or click on the little box icon to the right of the case text.

Where are the Test Cases?

Testpad's "test cases" are one-line prompts organised in an outline editor. Compared to other test case management tools (where a test case might be a more complicated item complete with pre-conditions, steps to execute, expected outcomes, priorities etc) they are certainly more simple and a lot faster to write.

Testpad keeps the concept of a test case deliberately more fluid. Sometimes a one-line prompt can encapsulate what would be a whole test-case in another tool. Sometimes, a sequence of Testpad rows, taken together, would map to another tool's single test case.

But that said, some customers construct more formal test cases using the outline structure in Testpad. Rows of text that aren't "testable" can be prefixed with // to make them a comment

Testpad prioritises ease of editing and maintenance over the formality of a test-case. How much detail you do or don't need to provide, per test case, depends on who you'll be asking to run the tests and how familiar they are with the product and how to test it.

Have a different question?

post some feedback

ask on twitter @testpadapp