SoftTelRG
Version 1.1.0Practical Learning Kit (lesson plan)

Guides

High-level product guidance for WebSureQTool. The guides are organized around three objectives: use the product, build suites, and troubleshoot. For click-by-click authoring help on any Learning Kit lesson, open the Intelligent Assistant.

Start here

Featured guides for the current release. Read these in order if you are new.

STEP 1
What's new in WebSureQTool 1.1.0
Version 1.1.0 ships with the Practical Learning Kit — a structured set of 13 step-by-step lessons that take a new user from first login to full happy-path automation. Lessons are followed in the Suite Editor; users build the suites themselves.
Tags: release, 1.1.0, what's new, changelog
STEP 2
Practical Learning Kit overview (v1.1.0)
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
STEP 3
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

Watch the setup walkthrough

A short video that takes you end-to-end: 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. If you prefer to read instead of watch, the guides above cover the same ground.

All guides

Foundations, learning paths, and reference material. For step-by-step authoring on any Learning Kit lesson (LK01–LK13), ask the Intelligent Assistant by lesson number.

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
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