ColdFusion Test Coverage Reports: Integrating TestBox With GitHub Actions and SonarQube

Test coverage tells you what percentage of your ColdFusion source actually runs under your tests — a low number means you’re under-tested — and you can generate, publish, and gate on it by wiring TestBox into GitHub Actions and SonarQube. The one ColdFusion-specific catch: TestBox’s code coverage requires a licensed copy of FusionReactor connected to the app under test (it’s what instruments the bytecode to track executed lines), easiest to run via CommandBox. Once coverage is on, TestBox can emit a SonarQube-compatible coverage XML directly (coverageSonarQubeXMLOutputPath), plus an HTML report. From there: in GitHub Actions you run the suite, produce the coverage report, and surface it on pull requests; in SonarQube you analyze CFML with the stepstone-tech/sonar-coldfusion plugin (a CFLint-based ColdFusion analyzer) and feed it the TestBox coverage XML so coverage shows on the SonarQube dashboard and a quality gate can block a merge that drops below your threshold. This guide covers enabling TestBox coverage, the FusionReactor requirement, the GitHub Actions pipeline, and the SonarQube integration — with config and workflow examples.
Read More