Skip to content

Plan and review tests in the browser

Prepare test plans in performed tests, add cases from the library and start runs from the plan. Test packages group related plans. You need the corresponding planning, editing and execution permissions.

Trees and actions

In planning and execution, the test library and requirements, the title column adapts to the available space. Long titles remain available on the tree entry. The action menu stays accessible on the right. Narrow layouts may move additional information into expandable row details.

Filter by custom result statuses

In Planning & execution, open Result statuses above the tree. Select up to 128 statuses defined in the project and choose Apply. No result yet finds variants without a saved result status. Custom statuses remain distinct even when they belong to the same category, such as two different failure statuses.

The filter uses the current result of each planned variant in its own test run. Earlier results and other runs do not count. Quick tests use their saved overall result. When the project variant feature is disabled, only the primary variant counts. Hiding variants in the tree does not change the filter scope. Matching tests and their parent nodes remain visible; templates without execution are hidden. Multiple selected statuses mean “any of these”. The existing run filter and text search restrict the selection further.

The selection is saved per user and project and is also used by Windows. It is independent of saved Web views. Reset result status filter clears it. A deleted status is shown as no longer available; deletion does not silently turn filtering off. The existing filtering permission and read access to the relevant tests are required.

When filtering during test execution is allowed, opening test execution carries over the status selection. If that setting is disabled, execution remains unfiltered. It then remains independent of later changes in the main tree and can be reset in the assistant. Matching tests are determined again after saving; Next does not skip a following match when the current test loses its previous status. Filtering does not change the run's scope, completion checks or report values.

Prepare a test plan

  1. Under Performed tests, open the plus menu and choose New test plan. Enter a title. Leave the checkbox selected to add test cases in the next step.
  2. Edit its name, description, attributes and attachments. Define the required test environments and review permissions.
  3. Select a test unit to include its visible child units and test cases. Clear individual checkboxes to include only part of a branch. Check the variants and confirm your selection.
  4. If library cases have changed since they were added, synchronise them and review the resulting plan content.
  5. Start a test run with the required details and cases. Check the chosen plan and environment before starting.

A plan contains the cases included for its execution. Library changes and plan changes therefore need separate review. Domain rules, including restrictions for plans with active runs, also apply in the browser.

With reusable test steps, the plan template receives explicitly selected block versions. Existing runs retain their content; new library versions do not update them.

Perform and follow up a test run

Open the run under test runs, read its instructions and expected result, and record the status, actual result, remarks and attachments. Link defects through the configured integration where required. Save before moving to the next case.

Next, Previous and Go to save the current case before navigating. Browser Back/Forward within test execution follows the same rule. If saving or loading fails, the displayed case remains open. Close saves and returns to the entry page, such as the filtered planning tree or run details; without a known entry page it opens the test-run list.

The browser warns before reloading or closing the tab when inputs have not been saved. Confirming that you want to leave can discard those inputs. There is no offline draft. The running timer alone does not trigger a warning.

Review the outcomes after execution and complete the run. Reopening, cloning, archiving and deleting are separate actions governed by permissions and run state. Before deleting or archiving, check the selected run and the consequences shown in the confirmation.

The web overview provides the basic execution steps.

Completed demo run showing progress and result distribution

Completed run from the live demo, showing progress and result distribution. Completion does not imply every case has a result. Configurable project terms and statuses remain partly German. Select image to enlarge.

Work with a package of plans

Open test packages, select or create the package and maintain its plans. When copying a package, choose the destination and whether to include all cases or only failed cases. Check start/end dates and archiving of completed runs where applicable. A package does not override execution permissions on its plans.

Review before execution

Open the case or requirement chapter and use its review section. Check the content, review status and existing feedback, then save your domain decision with the necessary rationale. Use the reviews area to follow up reviews across the project.

AI review can identify quality and coverage gaps. Accepting an AI finding does not replace a required domain approval or deliberately applying an edit.

For risk-oriented proposals, use AI test planning. For progress, failure patterns and exports, see reporting and data exchange.

Compare releases and record acceptance.