Start here: workspace, projects, suites, datasets, and runtime values

If you have not installed the app or imported a WebDriver yet, do the "Install and set up" guide first. Then use this page to build and run your first suite.

THE BUILDING BLOCKS (60 seconds)
- Project: the container for suites, datasets, pages, and reports. Created in the Project Explorer.
- Suite: one scenario, saved as a readable YAML file. Example: open login page -> type username -> type password -> click login -> verify dashboard.
- Step: one executable action - navigate, type, click, assert_text_equals, assert_visible, capture_text, wait, branch, loop, end.
- Dataset: planned input (usernames, passwords, expected values) in a key/value file.
- Runtime variables: values captured DURING a run by capture steps.
- The one rule: never use the same name for a dataset key and a runtime variable.

YOUR FIRST SUITE, CLICK BY CLICK
1. In the Project Explorer, click New Project (Web mode). Then click New Suite and give it a clear name, for example 01-first-check.
2. The Suite Editor opens. Pick your Browser (Edge or Chrome), enter the URL - for practice use https://wsqdemo.com - and click Open. A real automated browser window opens using your configured WebDriver.
3. Click Scan. The upper grid fills with every element found on the live page: Text, Selector, XPath, and a suggested Action per row.
4. Tick the Pick box for the elements you need, IN THE ORDER the flow runs (for a login: username field, password field, login button). Picked rows appear in the lower "Picked Activities (execution order)" list.
5. Edit each picked activity (Edit Selected...):
   - Inputs: Action = type. Value Mode = dataset with a key, or a literal value.
   - Buttons: Action = click.
   - Verifications: add an Assert (for example assert_visible or assert_text_equals) with the Expected value.
   - A Wait(s) of 1 second is a reasonable stabilizer on slow pages.
6. Use Add Step... for steps that scanning cannot give you: wait, url assertions, captures, and the final end step. Keep exactly one end at the bottom - START is automatic.
7. Click Save, then Run. Watch the browser replay your steps.
8. Read the log in the lower-right area. The FIRST line that says FAIL is the real problem; everything after it is downstream noise.
9. Click Open Flow to watch the same run as a step-by-step visual flow - useful for demos and for spotting where a long suite goes wrong.

RUN EARLY, THEN EXTEND
Author 2-3 steps, run, confirm, then continue. Catching a selector or dataset mistake at step 3 is minutes cheaper than finding it at step 30.

AFTER NAVIGATION, SCAN AGAIN
Steps belong to the page where they were authored. Every time the flow lands on a new page (or the page state changes after login, sort, or add-to-cart), click Scan again before picking new elements.

The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.