Working with test cases

Test cases are the core of Proba.run: each one describes a scenario to verify, organized into folders, tagged, and enriched with custom fields. This page covers creating and organizing cases, reusing steps, attaching files, filtering and searching, and recovering deleted items.

Creating a case

Open a project's workspace: a folder tree on the left, a list of cases for the selected folder on the right. Click New case, or press Enter while the case list is focused for a quick-add that creates a case directly in the current folder.

A case has:

• Title, description, and preconditions — free text.
• Priority and status — status follows a review workflow; see Case versions and review.
• Steps — either a structured list of {step, expected result} pairs, or a single block of free text (toggle between List and Text mode). In list mode, each case can also carry an overall Expected Result when using text mode for the steps field itself.
• Test accounts, tags, custom fields, and linked requirements.

Every case gets a permanent reference like QA-42 (project key + number), used in URLs, search, and links throughout the app.

Viewing a case

A case opens either in a side panel (from the case list, without leaving the list) or as its own full-page view (Open in fullscreen) — useful for sharing a direct link or reading a case at full width. Both views share the same tabs: Overview/Details (the case fields), Audit Log (a timeline of who changed what), and Runs (every time this case was executed, across all test runs).

From the case page you can also Duplicate a case (copies all fields, steps, tags, and custom field values into a new case in the same folder) or Delete it.

Organizing with folders

Folders form a tree inside each project, shown on the left of the workspace. You can create, rename, and delete folders, and drag and drop them to reorder or nest one inside another (dropping onto a folder nests it; dropping between folders reorders them). A folder can't be dragged into its own descendant.

Deleting a folder removes the whole folder along with everything nested inside it — see Deleted cases and folders for how to get it back. Cases inside a deleted folder move to trash together with it.

Within a folder, cases can be reordered by dragging their rows.

Tags and custom fields

Set up tags and custom fields for a project from Project settings.

• Tags are simple colored labels — give one a name and a color, then assign it to any case. A case shows up to two tags inline in the list, with a +N indicator for the rest.
• Custom fields let you capture structured, project-specific data on every case: text, multi-line text, number, date, dropdown, multi-select, checkbox, or URL. Each field can have a default value, a helper description, a required flag, and (for text/number types) a length or range limit. Fields marked Required must be filled in before a case can be saved.

When you create a new case, fields with a default value are pre-filled automatically; editing an existing case never overwrites values already saved on it. A date field's default can also be set to "always today," so new cases always start with the current date.

Reusing steps with shared steps

If several cases repeat the same sequence — logging in, preparing test data, cleaning up — create a shared step block once (in Project settings → Shared steps) and insert it into any case's step editor. A shared block appears in the case as a single named, read-only element among the regular steps; you can move or remove it as a unit, but its content is only edited in one place: the shared steps library.

Editing a shared block updates every case that uses it immediately, including how the steps appear when a test run is executed. A block that's still used by at least one case can't be deleted — you'll see how many cases reference it first.

Shared steps are only available when a case uses List mode for its steps; text-mode cases don't support them.

Attachments

While recording a result for a test case during a run, you can attach files — screenshots of a failure, logs, and similar evidence — directly to that result. Attachments show up as chips under the result in its history, and can be downloaded any time from there. Each upload is capped at 10 MB per file (50 MB total, up to 10 files at once); you can remove an attachment you no longer need.

Attachments can only be added while the run is open — a closed run must be reopened first.

Filtering the list

The case list toolbar lets you filter by priority, status, and tags at once, each as its own dropdown with checkboxes for multiple selections. An active-filter count and a Reset button next to it clear everything in one click. Filters are reflected in the page URL, so a filtered view can be shared as a link or bookmarked.

A search box filters cases by title as you type.

Saved filters (presets)

Once you've set up a combination of search, priority, status, and tags you use often, save it as a personal preset from the Presets menu. Presets are private to you — other project members don't see or share them. Applying a preset instantly re-applies its filters and jumps to the first page of results; deleting a preset doesn't change whatever filters are currently active on the list.

Searching across the project

Press Ctrl+K (or Cmd+K on Mac), or use the search button in the header, to open the global search palette from anywhere in the app. It searches projects, test cases, and test runs by name at once, scoped to what you have access to. Typing a case reference like QA-42 matches that case directly even if the number doesn't appear in its title.

Selecting a result takes you straight to it — for a case, that opens it in the case list with the side panel already showing its content.

Deleted cases and folders

Deleting a case or folder doesn't erase it immediately — it moves to the project's trash, visible only to project admins. From trash you can:

• Restore a case back to its original folder (or to the project root, with a notice, if that folder was deleted too), or restore an entire deleted folder along with everything that was inside it.
• Preview a case's content before deciding whether to restore or permanently remove it.
• Permanently delete (purge) a case — but only if it was never used in a test run. A case with execution history is kept in trash indefinitely, since run results are never allowed to lose their underlying data.

Everywhere else in the app — lists, search, pickers, reports — deleted cases and folders simply don't appear, as if they didn't exist.