Release notes · WebSureQTool 1.5.2
What’s new
WSQ Release 1.5.2: API testing the Postman way, with environments and encrypted secrets, a stricter command line for CI and AI agents, and fixes that keep your datasets safe and your exported tests quiet. It builds on 1.5: automation that keeps working behind single sign-on, projects you can run in one click, and a direct line for AI agents.
Available now on the Microsoft Store and GitHub.
New in 1.5.2
- API requests, Postman-style
- The API Testing tab gains a Requests tab: saved requests (method, URL, params, headers, auth, body) with checks (status, JSON path equals / contains / regex / exists, header, body, response time, OpenAPI contract) and captures that feed the next request: log in, capture the token, call with it. Copy as cURL, request History, a live row per request when you Run Requests, and Save Suite writes YAML.
- Environments and secrets
- Named environments (dev, qe, uat, prod) hold the base URL and variables, so one suite runs anywhere. Values marked secret are stored encrypted and masked in logs, reports and cURL. Import a Postman collection (v2.1) and environment; {{var}} becomes ${var}.
- Stricter command line
- wsq api-suite-run --suite <file> --env qe --json runs the requests and the spec scenarios from CI. An unknown --env now stops wsq web-run and wsq validate with exit code 2 instead of quietly running against the default base URL; wsq validate warns about mistyped keys; the MCP tools take an env.
- Encrypted dataset values stay encrypted
- The Suite Editor no longer rewrites a dataset with an encrypted value in plain text when it saves a value into the same dataset. Check datasets that hold secrets: an encrypted value starts with dpapi:; if a secret shows in plain text, tick Encrypted for that row in the Dataset Editor and Save.
- Fixes
- The Flow window follows the run; exported Java and C# tests start a quiet browser (no save-password, save-card or notification prompts); the use-case windows show the right version; new API suites save as YAML and existing JSON suites keep working.
Upgrading from 1.5.1? Nothing to migrate. Open each dataset that holds a secret once and confirm the value still starts with dpapi:; if not, tick Encrypted for that row and Save. See the videos on our YouTube channel for the Requests tab, environments and the web, API, web journey.
New in 1.5.1
- Nothing downloads without your consent
- WebSureQTool never downloads a browser driver: you import the one you choose with Tools > Import Driver (step-by-step video on our YouTube channel). Exported Java and C# projects never download drivers either. Automatic update checks are off by default; turn them on in the Help menu, and nothing installs without your click.
- Fits small and high-scaling screens
- At 1280 x 720 and above every action is visible: toolbars wrap instead of hiding Scan and Open, labels are no longer cut off, pages scroll on short windows and dialogs fit the screen.
- Scan finds the whole page
- In a narrow browser window, Scan now finds controls below the fold or past the right edge, such as a checkout wizard's Next button, and still leaves hidden content out.
- Browsers close when you're done
- Every browser window and driver WebSureQTool opened closes when the app, the command line or the MCP server exits. Browsers you attached to stay open.
Upgrading from 1.5.0? If you never imported a browser driver, import one once with Tools > Import Driver. Automatic update checks start off; turn them back on in the Help menu if you want them.
New in 1.5
Sign in once, test without a person present
Apps behind single sign-on and MFA no longer stop automation. Sign in once, and WebSureQTool saves the sign-in encrypted for your Windows user. Later runs load it, check it, and refresh it after every passing run, including headless, scheduled, CI and AI-agent runs. When the identity provider ends the session, the run stops and names the exact command to sign in again.
One-click starter projects
File > New Project from Starter Pack installs a ready-to-run project and runs its first suites: a demo shop, a banking-style site, our own practice store, an OpenAPI lab, and two live SoftTelRG products. Every project is yours to edit.
Use it from AI agents
A built-in Model Context Protocol server lets Claude, GitHub Copilot, Cursor and other MCP clients write, validate and run suites and read failures with screenshots. The command line adds JSON output, a step vocabulary (wsq describe) and suite validation (wsq validate).
Also in 1.5
- Persistent browser profiles
- Keep “stay signed in” cookies, passkeys and device-bound policies across runs.
- Attach to your browser
- Drive the Edge or Chrome you already opened, for identity providers that refuse automation profiles.
- OAuth 2.0 tokens
- A new step gets API tokens (client credentials, refresh token and more) and authorizes the following HTTP calls. Exports to Java and C#.
- Cookie banners and pop-ups
- A new step dismisses them only when they appear, so suites stay stable.
- Sturdier clicks
- A click covered by a sticky header is re-centred and retried; if something still covers it, the step names the covering element.
- Grouped checks fixed
- Assertion groups and empty expected values now behave exactly as written.
- Java and C# export of every step
- Exported tests now handle iframes, dialogs, drag and drop, uploads, shadow DOM, new windows, date pickers, loops, branches and data tables, and wait like the app does.
- Export from the command line (Pro)
- wsq export --with-project writes the tests plus a ready-to-run Maven or .NET project, so mvn test or dotnet test runs them in CI.
- Site Discovery
- Crawl a site, through its sign-in when you provide a dataset, and get page objects, proposed use cases and draft suites to review.
- Suite Editor fixes
- Steps keep the order you pick them, a rescan keeps your steps, Add Step enables the selector for click and type, and checks on scanned text, including regex checks, run as configured.
- Headless matches what you see
- Headless runs use a full 1920 x 1080 window, so a fixed footer no longer covers buttons and pages show their desktop layout.
- Session chains in CI
- A suite that signs in and a suite that continues in the same browser now run together headless, in the CLI and in CI.
- Modern web apps
- Clearing a field reaches React, Vue and Angular; URL and title checks wait for single-page navigation; date pickers understand today+7.
- Command-line runs from an installed copy
- WebSureQTool-CLI.exe and the new wsq.exe run your suites from Windows Task Scheduler, scripts and CI instead of opening the app.
Saved sign-in never bypasses MFA, CAPTCHA or bot detection: a person completes the first sign-in and WebSureQTool reuses what the identity provider issued. Upgrading from 1.3.3? Your projects run unchanged; regex checks now match anywhere in the text (use ^ and $ for an exact match), and headless runs now see a site’s desktop layout.
Ready to try WebSureQTool?
Free evaluation. Practice on the live web and API demo labs, or start from a one-click starter project.

