Working with quick test cases¶

A quick test case contains several short tests as rows in a table. It suits checklists that testers can complete without opening a separate test case for every row. Conventional and quick test cases can coexist in a project.

Enable quick cases and define a style¶

1. Enable quick test cases in global project settings.
2. Under Manage, open Quick styles.
3. Create a style with fields for the test-case definition and separate result fields for testers to complete.
4. On the additional settings page, select the default quick style. You can override the default for individual test units.

Fields can be checkboxes, dates, lists, editable links, number fields or single-line and multiline text. Result fields can additionally record the test result as a checkbox or list.

Create and execute a quick case¶

Right-click a test unit in the test library and select New quick test case. Enter a title and add the required rows. Use the row controls to reorder or remove rows, then save with OK.

Add the quick case to a test plan as usual. During execution, testers fill in the result fields for its rows. You can also import quick test cases from Excel.

Bug tracking and reports¶

Version 6 also supports creating, editing and executing quick cases in the web application.

• A linked bug belongs to the quick case's execution result, rather than to an individual row. The option to allow multiple bugs per test case controls additional links after the first bug; it is not required for the first link.
• Report preparation supplies quick rows and their results. Suitable run-result reports and test-plan handouts include dedicated tables. Custom templates must explicitly output those fields to include the required columns.

Check that your chosen report contains all fields and results needed for your quick style. See Reports and data exchange.