WebSureQTool as a testing tool: parameterized, requirements-based, reusable

WebSureQTool (WSQ) is an automated testing tool for web applications and REST APIs. This page maps WSQ 1.3.3 to the standard capabilities expected from the Automated Testing category, with the exact places each one lives in the product.

PARAMETERIZED & DATA-DRIVEN TESTING
- Any step value can be a parameter: set Value Mode to dataset and reference a key, or use ${VARIABLE} placeholders such as ${LOGIN_USER}, ${FIRST_NAME}, or ${POSTAL_CODE} directly in the step.
- Parameters resolve from environment-aware CSV/JSON datasets stored in your project (for example dev.csv, qa.csv, uat.csv). One suite runs across environments and data rows without editing a single step — promote the same regression suite from dev to QE to production checkout with a data swap.
- The Dataset panel shows the active dataset and its keys, with Edit, Duplicate, and Validate Keys tools, so parameter problems are caught before a run.
- Runtime parameters are supported too: capture steps save values during execution (for example ${RUNTIME_CART_COUNT}) for reuse in later steps and assertions.

MOVE & COPY
- Right-click any step or flow node to duplicate, copy, or paste. Duplicate N Times builds repeat-heavy flows in seconds.
- Datasets can be duplicated for new environments or scenarios.
- Suites are portable, plain-text YAML files — copy or move them between projects, share them with teammates, or version them in git like any other source file.

REQUIREMENTS-BASED TEST DESIGN
- Suites are organized as named use-case scenarios (for example 01-happy-login-cart-checkout), so each suite maps to a requirement or user story your team already tracks.
- Every step can carry explicit assertions — assert_visible, assert_exists, assert_text_equals, assert_attr_contains, and grouped multi-assertions — that encode the expected behavior from the requirement into the test itself.
- Execution is deterministic: a WSQ suite performs exactly the steps and checks it declares, in order, every run. Tests verify what the requirement specifies — they never improvise steps.
- Because suites are readable YAML, business stakeholders can review that a test matches its requirement without reading code, and JUnit-friendly XML output lets teams tie results back to requirements in their existing ALM and CI tools.

REGRESSION TESTING & EVIDENCE
- The Run Panel executes one suite or a selected batch sequentially, with pass/fail status, duration, and a per-suite report folder.
- Every run produces evidence you own: HTML reports, logs, screenshots, run.json, and JUnit-friendly outputs (Reports & Execution History are Pro features).

Together these make WSQ a complete authoring-to-evidence testing tool: parameterized suites your whole team can build visually, organized around requirements, reusable through Move & Copy, and verified by deterministic runs.

The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.