Skip to content
- Projects with a key (
SHOP), a suite tree, cases with keys like SHOP-12.
- A case: description, preconditions, steps “action → expected result”, priority, type, status, tags, automation
key.
- Formatted texts: the description, preconditions and steps can be bold, italic, underlined, in another font or size, with
lists and tables — a toolbar in the case and shared step editors. They are stored as Markdown (GFM tables;
underline, fonts and sizes as inline HTML), so case files, search, diffs and exports keep working, and texts
written before stay as they were.
- Every change of a case keeps a full version; concurrent edits are caught (
expectedVersion).
- A case page shows its results in all runs.
- Attachments to a case result in a run and to the case itself: drag and drop, choosing files, pasting a
screenshot with Ctrl+V. Images (PNG, JPEG, GIF, WebP) are shown as thumbnails, videos (WebM, MP4) with a player,
other files are downloaded. Screenshots of a failure are visible in the run and in the result history on the
case page. The type is detected by the content, not the name; executables and scripts are not accepted.
Identical files are stored once; a file is deleted with its last owner (case, run, project).