CI/CD integration: use JUnit XML + run.json as the automation contract
Tags: ci, cd, pipeline, junit, run.json, azure devops, github actions, jenkins, cicd
What it is Guidance for using run artifacts (especially junit.xml and run.json) as a stable contract between WebSureQTool and your CI/CD pipelines. Why it’s needed - Pipelines need machine-readable results to gate releases. - Teams need consistent evidence for audits and sign-off. - A stable output contract reduces integration complexity. Benefits - Drop-in pipeline integration (JUnit is widely supported). - run.json can be used for custom dashboards or trend analysis. - Separates test authoring from test execution infrastructure. How to use it in WebSureQTool Option A: Use Pro CodeGen to generate a Java/.NET project and run it in CI. Option B: Use WebSureQTool locally for authoring and use artifacts as evidence for manual sign-off. Publish junit.xml to your CI test reporting (Azure DevOps, GitHub Actions, Jenkins, etc.). Archive run.json and report.html per build/release for audit trails.