Roadmap
Items under active development exist in development builds today. We list a capability on the main site only when it ships in a public release — so what you read elsewhere on this site is what the current version actually does.
Current public release: 1.3.3. See What’s new for what shipped most recently.
In active development
Locator Health & deterministic self-healing
In developmentEach step carries ranked fallback locators. At run time WSQ tries the primary locator first, falls back in a fixed and readable order, and logs exactly which locator matched — a heal ledger you can audit. A Locator Health view tracks success, failure, and heal rates so brittle areas rise to the top and you fix them deliberately. Healing never invents locators or mutates your suite.
Guided use-case journeys
In developmentScan an application once and WebSureQTool discovers its page and state structure, then assembles end-to-end business journeys — for example login → cart → checkout → confirmation — as runnable, editable use cases built from your page objects and datasets.
Performance/Load: preview to general availability
Preview (Beta) todayThe Performance/Load preview in the current release replays a journey across concurrent sessions and aggregates p50/p90/p95/p99 latencies plus error rate. Roadmap work hardens this into a fully supported capability.
Backlog — future enhancements
Designed-for capabilities we will bring forward based on user demand. They are part of WSQ’s architecture today, but not scheduled for the next release.
API CodeGen (Java & C#)
Backlog · demand-drivenExport API suites as standalone HttpClient test code — the same ownership model as Web CodeGen today, self-contained and CI-ready. WSQ's architecture is designed to support this capability; we will schedule it based on user demand. If this matters to your team, tell us on the Contact page — real usage drives prioritization.
Scheduler & Windows Task bundles
Backlog · demand-drivenRecurring in-app schedules plus exportable Windows Task bundles: a portable workspace subset and runner that executes unattended via Windows Task Scheduler, even when the app is closed. WSQ's architecture is designed to support scheduled, unattended execution; we will schedule this work based on user demand — if your team needs it, tell us on the Contact page.
A note on how we announce features
Timelines here are directional, not commitments — items ship when they meet the quality bar, and scope can change based on what evaluation and enterprise users need most. If one of these capabilities is a prerequisite for your team’s adoption, tell us via the Contact page — real usage is how we prioritize.

