You now have more control over how mabl tests a code change at each stage of your workflow, from opening a pull request to deploying to staging. With change validation, you choose the suites that always run at each stage, and mabl adds the tests the change actually affects, found by test impact analysis (TIA), which we released last month. Your CI pipeline then gets a clear answer for each stage: let the change through, or block it.
For example, run your smoke suite and the impacted tests on every pull request, and block the merge only if the smoke suite fails.
Early access
Change validation is in early access for accounts with generative AI features. Pricing and packaging are subject to change.
How it works
A policy file in your repository, .mabl/policy.yaml, lists the checks for each stage of your workflow. Here is the policy for that example:
version: 1
suites:
smoke:
plan_labels: [smoke]
applications:
web:
mabl_application: '[application-id]'
target:
environment: '[environment-id]'
stages:
pull_request:
checks:
- kind: suite
suite: smoke
must_pass: true
- kind: impacted
With the policy file, you can:
- Choose which impacted tests run. Keep impacted tests to the plans and labels you pick, and leave out tests that run long or that you've labeled to skip.
- Add suites to any stage of your workflow. Run a fixed set of plans, such as your smoke tests, alongside the impacted tests or on their own, when a pull request opens, when it enters the merge queue, after a merge deploys to a shared environment, or at any other stage you define.
- Block a merge on the checks that matter. Mark the checks that must pass, and let the rest report their results as warnings.
The policy can also waive a check for one pull request, and keep mabl branches in step with your code. See Set up a mabl policy file.
To get started, see Run change validation from your own CI. If your repository is on GitHub, the mabl change validation GitHub Action sets it up for you.
Share feedback
We'd love to hear how change validation works for your team. Share feedback with your mabl customer success manager (CSM), or add it in the mabl Product Portal.