Run Panel: batch runs, logs, and consistent execution
Tags: run panel, batch, runs, logs, execution, regression
What it is Run Panel executes suites consistently and captures structured results and logs. Why it’s needed - Teams need repeatable execution, not ad-hoc clicking. - Stakeholders need evidence (pass/fail, timings, assertions, screenshots where applicable). - Batch runs are required for regression and BAU checks. Benefits - Consistent execution with organized outputs. - Supports batch runs (smoke/regression suites). - Produces artifacts that integrate with CI/CD and reporting workflows. How to use it in WebSureQTool 1) Select one or more suites to run. 2) Choose dataset and environment (if applicable). 3) Run batch execution and review logs in real time. 4) Export/collect artifacts for release evidence (run.json, report.html, junit.xml).
