QalionQALION

Test cases

A test case describes one behavior to check. The AI agent reads it and carries it out in the browser, so write it the way you would brief a colleague.

Folders and smart views

Click Test cases in the sidebar. The folder tree is on the left, the cases of the selected folder on the right, and the editor opens in a side panel.

  • Every case lives in a folder. Use Create folder and New subfolder; folders nest as deep as you need.
  • Drag folders and cases to move them. Qalion asks you to Confirm move first.
  • Select several folders to export or delete them together.

Smart views list cases from every folder: All test cases, Failing, Flaky, Never run, Stale · 30 d+, Written by AI · review, No requirement and In no plan.

Test cases: folders and smart views on the left, the cases with their last results and requirements on the right.

Create a test case

1
Select a folder and click New case. A case called "Untitled test case" is created and opens in the editor.
2
Type a title that says what the test verifies. Titles must be unique within a folder.
3
Write the test in the case's format (see below) and fill in the fields you need.
4
Set Status to Active when the case is ready to run.

The editor saves as you type. Its header shows Saving…, Unsaved or Saved, or "A title is required to save".

The case editor: status and marks at the top, then the requirement it proves, the description and the steps.

You can also Import cases from a file, or click Generate with AI to ask the Qalion AI to draft them. The editor's menu has Copy link, Duplicate and Delete, and its Run button starts a quick run of this case.

Formats

FormatHow you write it
StepsRows of Action and Expected result. Each step can carry images, which the agent receives as reference. Drag to reorder.
GherkinA Given / When / Then scenario. Qalion turns it into steps when the case runs.
Free textSay what to do and what must happen, in your own words. The agent turns it into steps when it runs.
Gherkin scenariotext
Given I am on the login page
When I type $username in the Username field
And I type $password in the Password field
And I click Login
Then the Products page opens

The project's default format is set under Configuration → New cases start as. Each case can change its own format.

Tip
Keep one behavior per case, and make each expected result something visible on the page: a message, a heading, a value in a field. $username and $password above are dataset columns; see Shared steps & datasets.

Fields

FieldValues
TitleRequired, unique within the folder
StatusActive, Draft, In review, Outdated or Rejected
PriorityCritical, High, Medium (default) or Low
TypeFunctional (default), Regression, Smoke, Integration or Other
AutomationManual (default), In progress or Run by agent
TagsFree labels. Press Enter, Space or a comma to add one.
OwnerThe person responsible for the case
DescriptionRich text with images: context, preconditions, what matters
IDRead-only, for example CHK-101
Note
Priority, Type, Automation and Tags help you sort and filter. They don't decide whether a case runs. Only the Status does.

The editor also shows the case's last result and history per browser profile, its open problems, the plans that use it (the History · Problems · Plans row) and the requirements it proves.

Statuses and what runs

StatusMeaning
ActiveReady. Active cases run.
DraftBeing written. New cases start as Draft.
In reviewWritten by Qalion AI and waiting for your review.
OutdatedNo longer matches the app.
RejectedNot kept, for example a Qalion AI draft you turned down.
Warning
When a plan or a selection contains at least one Active case, only the Active cases run. The others are skipped, and the plan marks them "Not Active — skipped when the plan runs". If none of them is Active, they all run.

Search, filter and sort

  • Search by title, ID or step text.
  • Filter by Status, Priority, Health (failing, flaky, stale, never run, passing) and Target (browser profile).
  • Results on picks the environment whose last results and health the list shows.
  • Sort by Last updated, Title, Priority or Health.

Bulk actions

Tick cases in the list to act on several at once: Run selected, Add to plan, Move, Duplicate, Assign (owner), Export and Delete.

Import

Click Import to open "Import test cases". Qalion accepts CSV, JSON and XML files up to 5 MB.

FormatWhat Qalion reads
CSVA header row with any of: title, description, steps, expected, folder, priority, tags. Each row becomes one case with one step (steps + expected). Separate tags with ; or |.
JSONAn array of cases, or { "folders": [ { "name": …, "testCases": [ … ] } ] }. A case has title, description, steps (action, expectedResult), priority and tags.
XMLSquash TM exports (test-suite, test-case and step elements).
  • Cases go into the selected folder. When the file names folders, Qalion creates them. With no folder at all, cases land in a folder called "Imported".
  • Imported cases are created as Active, so they run as soon as they are in a plan. Review them, including their priority, before you run them.

Export

  • Select cases and click Export for a CSV with their latest results on the environment chosen in Results on, flakiness, requirements and owner.
  • Select folders and export them for a CSV with Folder Path, ID, Title, Status, Priority, Type, Automation, Tags and Description.

Trash

Deleting moves folders, test cases, requirements, shared steps, datasets, environments, test plans and projects to the Trash. Restore them from there for 30 days; after that they are deleted for good. Owners and Admins can also Delete forever or Empty trash.

Warning
Test runs don't go to the Trash. Deleting a run is permanent.

Was this page helpful?