Solution Checker¶
DGT-TST-020 — Run the Power Apps Solution Checker against every packed solution as a build-pipeline quality
gate — step 8 in Build Pipeline, after packaging and before
automated tests.
Running it¶
In Azure DevOps, use the PowerPlatformChecker@2 task from the
Power Platform Build Tools
extension — see Azure DevOps. In GitHub Actions, use
microsoft/powerplatform-actions/check-solution@v1 — see GitHub Actions.
Both wrap the same underlying Solution Checker service pac calls directly.
What it catches¶
The checker flags plugin code issues (e.g. blocking synchronous calls, unhandled exceptions in patterns it recognizes), customization issues (e.g. missing index recommendations, unused attributes), and general solution-quality findings. It does not replace server-side unit tests — it's static analysis against the packaged artifact, not a test of your plugin's actual behavior against representative data.
Gating the build¶
Treat a failing high-severity result as a build failure, not a warning to review later — configure the task/step to fail the pipeline on high-severity findings rather than only reporting them. Lower-severity findings are worth tracking but shouldn't block every deployment on their own; use judgment per project on where that line sits, and document the chosen threshold in the project's architectural documentation if it deviates from "fail on high."