Skip to content

WebSureQTool 1.5.2

Latest

Choose a tag to compare

@softtelrg softtelrg released this 05 Nov 01:13
dd5c6d9

WebSureQTool 1.5.2

WSQ release: API testing the Postman way with environments and encrypted secrets, fixes that keep your datasets safe and your exported tests quiet, and a stricter command line for CI and AI agents.

Install: Microsoft Store, or download WebSureQTool-1.5.2.msi below (Windows 10/11, 64-bit, signed by SoftTelRG LLC).

Highlights

  • API Testing, Postman-style. An API suite now holds 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 (a JSON path, header or status into a variable for the next request). Auth: none, bearer, basic, API key, OAuth 2.0 client credentials. Import Postman collections (v2.1) and environments; {{var}} becomes ${var}.
  • Environments for API projects. api-projects/<project>/environments.yaml holds named environments (dev, qe, uat, prod) with variables; values marked secret are stored encrypted and shown as ******** in logs, reports and cURL.
  • Stricter command line. wsq web-run --env uat and wsq validate --env uat exit 2 with "Unknown environment 'uat' for project 'Shop'; known: dev, qe" instead of quietly running against the default base URL. wsq validate warns about mistyped keys ("did you mean 'selector'?"). The MCP tools wsq_validate_suite and wsq_run_suites take an env argument. New: wsq api-suite-run --suite <file> [--env qe] [--json].

Fixes

  • Encrypted dataset values stay encrypted. The Suite Editor no longer rewrites a dataset with an encrypted value in plain text when it stores 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.
  • The Flow window follows the run. Long suites no longer run off the bottom of the window.
  • Exported Java and C# tests start a quiet browser. Code Gen and wsq export give the exported Selenium tests the same browser settings WebSureQTool uses: no save-password, save-card or autofill prompts and no notification bubbles over the page under test.
  • The use-case windows show the right version. The Orchestrate canvas and the use-case editor showed "WSQ 1.4.1"; they now show the version you are running.
  • New API suites save as .yaml; existing .json suites keep working. Scenario names read "Happy Path" and "Invalid Body" instead of HAPPY_PATH.

Upgrading from 1.5.1

Nothing to migrate. Check datasets that hold secrets as described above.

Full guides: https://www.websureqtool.com/docs · What's new: https://www.websureqtool.com/whats-new · Videos: https://www.youtube.com/playlist?list=PLUfTRQD_nBlA