Run the test cases already in your spreadsheet

A .xlsx, .xls or .csv with a Title column and a Steps column. Several steps go in one cell, one per line — the way you would write them anyway.

• —One row per case, or one row per step with the title repeated — both layouts are read.
• —Headers are matched case-insensitively, and the common synonyms for each column are accepted.
• —A row it cannot read is reported by row number with the reason, rather than dropped quietly.
• —Nothing is installed and no browser extension is involved: the file is the input.

A grammar turns each line into an action. It is the same compilation every time, so the same sheet produces the same run today and next month.

• —A line the grammar cannot place is refused and named — it never becomes a step that quietly does nothing.
• —Steps resolve against the Knowledge Base your exploration built, with the confidence that chose each element visible.
• —A weak match is refused rather than clicked, so a passing run means the steps it says it ran.
• —No model is consulted while a test runs. The verdict does not depend on a third party being up.

A real Chromium session against your application, with what happened kept per step rather than summarised at the end.

• —A screenshot per step, and a video recording of the run.
• —Per-step pass or fail, with the element that was chosen and why.
• —Values read during the run, shown against the step that read them.
• —The whole thing exported as a Word report.

The two columns

• Title — The case name. "Name" and "Test Case" are read the same way.
• Steps — The steps, one per line in the cell. "Description", "Actions" and "Test Steps" are read the same way.

What it needs from you

• —A spreadsheet with a title and steps. If the steps are prose rather than instructions, the lines that cannot be placed come back unread.
• —One exploration of your application, so the Knowledge Base has something to resolve the steps against. The demo example needs none.
• —A browser. There is nothing to install.