Version 1.5.2Practical Learning Kit (lesson plan)
Guides
High-level product guidance for WebSureQTool, organized around three objectives: use the product, build suites, and troubleshoot.
Prefer to ask in your own words? Try the Intelligent Assistant — the same guidance, answered conversationally.
Start here
Featured guides for the current release. Read these in order if you are new.
STEP 1
Install and set up WebSureQTool on Windows
From download to your first passing test: install the app, choose a workspace, import your browser driver, and run a starter project.
Tags: install, download, where to download, github release
STEP 2
Starter projects: install a ready-to-run project in one click
File > New Project from Starter Pack installs a complete, editable project and runs its first suites, so you learn from tests that already pass.
Tags: starter projects, starter pack, examples, sample suites
STEP 3
What's new in WebSureQTool 1.5.2
WebSureQTool 1.5.2: Postman-style API requests with checks and captures, environments with encrypted secrets, Postman import, a stricter command line, and fixes for encrypted datasets and exported tests; on top of 1.5.1's consent-only drivers and 1.5's saved sign-in, starter projects, and MCP server and CLI.
Tags: 1.5.2, 1.5.1, 1.5.0, api requests
All guides
Foundations, learning paths, and reference material.
Start here: workspace, projects, suites, datasets, and runtime values
Understand the core building blocks before you create suites. This is the shortest path to using the product correctly.
Tags: getting-started, workspace, project, suite, dataset, runtime variables, page, step
Running suites: Editor Run, Run Panel, Flow View, and reports
Three ways to execute the same suite - quick runs from the editor, configured runs from the Run Panel, and the visual Flow View - plus where the evidence lands.
Tags: run, run panel, flow view, open flow, headless, shared session, reports, run history, junit, html report
WebSureQTool as a testing tool: parameterized, requirements-based, reusable
How WSQ delivers parameterized data-driven suites, Move & Copy step tools, and requirements-based test design with deterministic execution.
Tags: automated testing, testing tool, parameterized testing, data-driven testing, requirements-based testing, move and copy, duplicate, regression testing, assertions, deterministic
Web learning path: the 12 core capabilities
Learn WebSureQTool in the right order: start small, add one capability at a time, then move into realistic multi-step flows.
Tags: web, 12 features, single assertion, wait, regex, data validation, multi-assert, repeat, store reuse, url capture, session capture, branch, recovery, loop, managed session, happy path, saucedemo, parabank
API learning path: from first GET to authenticated flows
Start with a direct GET, then add POST, parameters, authentication, and spec-driven requests in that order.
Tags: api, get, post, query params, json, auth, token, bearer, openapi, spec
Live demo labs: practice on wsqdemo.com (web) and api.wsqdemo.com (API)
Two always-on public targets so you can practice WebSureQTool without standing up your own app or API.
Tags: demo, practice, sandbox, wsqdemo, api.wsqdemo.com, openapi, swagger, base url, spec, lab
Datasets vs runtime values
Datasets are planned input. Runtime values are captured output. Keeping them separate makes suites easier to debug and scale.
Tags: dataset, runtime, store, reuse, capture, variables
Practice models: how to go from demo to production
The safest learning pattern is clone, tweak one thing, run again, then adapt the structure to your own app.
Tags: practice, learning, clone, adapt, saucedemo, parabank, production
Free vs Pro: trial, release scope, reports, and Web CodeGen
Use the evaluation path first. Pro unlocks reports and Web CodeGen when those outputs become necessary.
Tags: free, pro, trial, pricing, reports, web codegen, scheduler, api codegen, subscription
Reports, artifacts, and Web CodeGen
Pro adds stakeholder-friendly evidence and exported web test code, while your workspace stays local-first.
Tags: reports, artifacts, history, web codegen, java, c#, junit, html
Technology stack and source-code licensing
WebSureQTool is built in Java, uses Selenium WebDriver for browser automation, and can be licensed for internal source-based development under a separate agreement.
Tags: java, selenium, webdriver, opensource, source code, licensing, ip, internal use
Troubleshooting: a structured playbook for Web and API failures
A structured playbook for diagnosing failures: read the log first, isolate the failing step, then work down a fixed checklist by category (selector, data, action, wait, assertion, session, branch/loop, API).
Tags: troubleshooting, errors, element not found, stale, base url, 401, 415, selector, log, scan, webdriver, dataset, runtime, session, branch, loop
What's new in WebSureQTool 1.3.3 (previous release)
Version 1.3.3 adds in-app update notifications for direct installs, automatic browser session recovery, and smarter handling of pasted URLs.
Tags: release, 1.3.3, changelog, updates, update notification, browser session, bug fixes
Practical Learning Kit overview
The Practical Learning Kit is a 13-lesson build path. Each lesson states the business objective, the risk, and the exact authoring sequence. Users follow the lesson and build the suite themselves in the Suite Editor.
Tags: learning kit, lk01, lk13, saucedemo, dataset, business workflow, build suites
Saved sign-in for SSO and MFA apps: sign in once, run headless
Automate apps behind single sign-on and MFA: sign in once, and headless, CI and AI-agent runs reuse and refresh the encrypted saved sign-in.
Tags: sso, single sign-on, mfa, saved sign-in, auth state, entra id, okta, headless, ci, session, persistent profile, attach browser, oauth2
Use WebSureQTool from AI agents (MCP server)
WebSureQTool ships an MCP server: Claude, GitHub Copilot and Cursor can write, validate and run real browser tests and read failures.
Tags: mcp, model context protocol, ai agents, claude, claude code, github copilot, cursor, ai testing, llm, automation
Command line and CI: run, validate and export suites with wsq.exe
Run suites headless with wsq.exe for CI/CD: JSON results, clear exit codes, validation before a browser opens, and Java/C# export (Pro).
Tags: cli, command line, ci, cd, pipeline, headless, json, exit codes, jenkins, azure devops, github actions, export, java, c#
Locator Health: see which locators are brittle
When a CSS locator stops matching, WebSureQTool tries the recorded XPath and logs it; Locator Health (Pro) shows which locators are brittle.
Tags: locator health, locators, self-healing, fallback, xpath, css, flaky tests, maintenance
API requests, environments and Postman import (1.5.2)
Build Postman-style requests with checks and captures, keep base URLs and secrets in named environments, import a Postman collection, and run the suite from the command line.
Tags: api, requests, postman, postman alternative, environments, secrets, capture, checks, bearer token, curl, api-suite-run, ci, yaml
Need a specific Learning Kit lesson?
The 13 Learning Kit lessons (LK01–LK13) are delivered through the Intelligent Assistant so each lesson opens with full step-by-step authoring detail. Ask for a lesson by number — for example, “walk me through LK05” or “how do I build LK11 in the Suite Editor”.
Open Assistant
