Build your first web suite (YAML) and run it
Tags: suite, yaml, run, report, selenium
What it is A practical walkthrough: create suite.yaml, bind data, run, and review artifacts. Why it’s needed - Teams need a quick path from install → first successful run. - A working example clarifies the suite structure and outputs. - Early success reduces adoption friction. Benefits - Fast onboarding for dev and QA. - A repeatable ‘known good’ smoke suite. - Creates a baseline artifact set for governance. How to use it in WebSureQTool 1) Create a new suite in the Suite Editor (e.g., Login smoke). 2) Add steps: navigate → type → click → assert. 3) Optionally bind a dataset for credentials or base URLs. 4) Run from Run Panel. 5) Review outputs: logs + run.json (and report.html / junit.xml depending on configuration).
