Download WebSureQTool
The simplest way to install WebSureQTool on Windows is from the Microsoft Store. Click the install badge below and Windows will handle the rest.
Or open the Store listing directly: websureqtool on Microsoft Store ↗
Setup walkthrough
Follow along as you install — the video matches the install flow step by step.
A short end-to-end walkthrough: install from the Microsoft Store, set up your local workspace and SSO, configure WebDriver for Edge or Chrome, import sample suites from GitHub, and run your first Web UI and API test. Play it on a second screen or phone and pause as you go.
Build test suites with AI (ChatGPT, Claude, Copilot, Gemini)
Paste this prompt into any AI assistant — ChatGPT, Claude, GitHub Copilot, Gemini, or a local agent — then describe the test you want in plain English. The AI returns ready-to-paste WebSureQTool YAML grounded in the actual action and assertion schema, so you can drop the output straight into the Suite Editor.
The prompt is ~3 KB and covers both the conceptual model and the full YAML schema. The AI you paste it into will use it as context for every subsequent message in the same conversation.
What’s new in WebSureQTool 1.1.0
- 13 step-by-step lessons (LK01–LK13) covering login, sort, cart, checkout, session reuse, branch/recovery, loops, runtime capture, browser-state evidence, grouped data validation, and a final golden-capability demo.
- Each lesson states the business objective, the business risk, and the exact authoring sequence in the Suite Editor.
- Suggested dataset filenames (for example
data/default.csv) are conventions you can adopt — you create the file with the keys each lesson asks for. - Step-by-step authoring help for any lesson is available through the Intelligent Assistant.
- Project + suite + dataset first. Avoid hard-coding usernames, ZIP codes, or expected text inside the suite. Keep them in a dataset for reuse and review.
- Pick UI elements in flow order. Username, password, login button — in that order — so picked activities map cleanly to the user journey.
- Run early, then extend. Click Run after the first 2–3 steps. Catch selector or dataset mistakes before the suite gets long.
- Capture-first, assert-separately. LK11 documents the cleanest way to validate URL, title, and browser storage without mixing capture with assertions.
- Session continuity. LK06 + LK07 split a workflow across two suites without repeating the login overhead.