Applitools Eyes "New (unresolved) ... requires baseline approval" in CI
Applitools compares each checkpoint against an accepted baseline. A "New" step has no baseline yet and an "Unresolved" step differs from the baseline. Both make eyes.close() throw until someone accepts or rejects the result in the Test Manager.
What this error means
The test fails at eyes.close() with a message that new or unresolved steps were found, linking to the Applitools Test Manager. The build stays red until the baseline is reviewed there.
com.applitools.eyes.exceptions.DiffsFoundException: Test 'Home' of 'MyApp'
detected differences! See details at:
https://eyes.applitools.com/app/test-results/...Common causes
A new checkpoint with no baseline
The first time a checkpoint runs, Applitools marks it "New." It needs a human to accept it as the baseline before it can pass.
An unresolved difference awaiting review
The checkpoint differs from the accepted baseline. Applitools will not auto-decide whether the change is intended, so it reports "Unresolved" and fails the test.
How to fix it
Accept or reject in the Test Manager
- Open the linked Applitools Test Manager result.
- Accept the checkpoint to set or update the baseline if the change is intended, or reject it if it is a regression.
- Re-run so the now-accepted baseline passes.
Separate baselines by branch
Set the batch and branch info so feature branches compare against the right baseline and merges promote it cleanly.
Configuration config = new Configuration();
config.setBaselineBranchName("main");
config.setBranchName(System.getenv("GITHUB_HEAD_REF"));How to prevent it
- Review and accept new checkpoints in the Test Manager.
- Set baseline and feature branch names so comparisons target the right baseline.
- Treat "Unresolved" as a required review, not a flaky failure.