Reporting(Playbooks & CLI)
After a playbook has run, a new playbook run entry appears in the playbook overview. From there, you can inspect results, open details, and use several export options. Besides the dashboard overview (which shows all runs from the past month), JOSF provides multiple reporting features to generate management-ready summaries, accessibility reports, and machine-readable test output.
1. Management Report Export
From each playbook run you can open the Export dialog (see screenshot).
This window allows you to generate a management report containing key information about the application under test and the context of the run.
In this export dialog, you can provide:
- Application name(s)
- Version information
- Optional metadata fields (e.g. Team name, Test Manager, Release number)
- Management summary for high-level notes
- Detail level, to control how much of the execution data is included
Once exported, JOSF generates a structured management report that is easy to share with stakeholders who want a high-level overview without navigating the UI.
2. Accessibility Report Export
When accessibility scans are part of your test suite, JOSF can generate a dedicated Accessibility Report.
This export:
- Collects all accessibility scan results from the playbook run
- Compiles them into a detailed summary
- Generates a PDF report that highlights violations, impacted elements, severity, and guidance for remediation
This PDF is designed for teams working with WCAG compliance, QA engineers, and accessibility specialists.
3. JUnit Export via the CLI
When you execute a playbook from the CLI, JOSF automatically generates a JUnit XML report.
- The file is namedÂ
junit-repor-[timestamp]t.xml - It is written directly to the current working directory where the CLI command was executed
- This format is compatible with CI/CD systems such as Azure DevOps, GitLab, GitHub Actions, Jenkins, and many others
You can use this file for:
- Azure DevOps Test Plans
- Build pipelines
- Test reporting dashboards
- Automated quality gates
This makes the CLI workflow fully CI-friendly and ensures that test results integrate seamlessly into existing development pipelines.
In Summary
JOSF provides three complementary reporting mechanisms:
| Reporting Type | Purpose | Output Format | When to Use |
|---|---|---|---|
| Management Report Export | High-level summaries for stakeholders | PDF-like management report | After a run, manual review or reporting moments |
| Accessibility Report Export | Detailed accessibility findings | When accessibility scans are part of the test suite | |
| JUnit XML Export (CLI) | Machine-readable CI/CD reporting | junit-report.xml | Automated pipelines, Azure Test Plans, integrations |