Code Coverage and Quality Roadmap

Project-wide engineering improvement for the Magento 2 and Adobe Commerce plugin, covering the entire Java and Kotlin production codebase. This is independent of App Builder support.

Roadmap item

• CI coverage collection, badges, and code quality. Gather coverage from all test types, make results visible, increase coverage to at least 95%, and improve maintainability.

Coverage and code-quality acceptance criteria

• Collect and merge production-code coverage from unit, IDE/platform integration, MCP end-to-end, and UI tests, including plugin code executed inside IDE processes.
• Publish combined and separate Java/Kotlin reports in CI, with coverage badges linked to the reports. Merge execution data rather than averaging test-suite percentages.
• Reach at least 95% line coverage for Java, Kotlin, and the combined production codebase; report branch coverage alongside it. Keep exclusions limited to documented generated or third-party code.
• Add meaningful regression, failure-path, and boundary-case tests, and refactor complex or duplicated code to improve maintainability.
• Enforce the coverage target and code-quality checks in CI once the baseline reaches the target, and prevent subsequent regressions. Missing test-suite coverage must be visible rather than silently treated as complete.