- Get Started
- Functionality
- Learning
- Extension
- Dev Tooling
- APIs
- Releases
Changed on:
9 Nov 2026
| Level | Runs | Catches |
| Rule unit tests | Every push, in the module build | Logic errors in a single rule |
| Workflow checks | Every push | Broken workflow structure, rules referenced but not shipped |
| Post-deploy verification | After every deploy | A deploy that reported success but did not install what was built |
| Live end-to-end | After deploying to dev | Rules and workflows that misbehave together on a real account |
`util-test` library (`RuleExecutor`, mocked GraphQL responses, action assertions) and keep them next to the rules in the plugin reactor. They run inside `mvn package`, so a failing test stops the module build.`check`) and raise it as coverage improves. Never lower it to get a build through.`package`, not `test`. If the rules module unpacks JARs from other reactor modules, `mvn test` on a clean checkout fails before any test runs, because those JARs are only built during `package`.`module.json` or provided by a reference module,`<ACCOUNT>.<module>.<RuleClass>`).