Guides
High-level product guidance for WebSureQTool. For detailed step-by-step learning, use the Intelligent Assistant.
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
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
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: fast fixes for common Web and API failures
Most failures come from selectors, waits, expected values, runtime variable names, or missing API setup. Start there.
Tags: troubleshooting, errors, element not found, stale, base url, 401, 415, selector