Skip to content

Commit be05ef2

Browse files
JeeveshJ7JeeveshJ7
authored andcommitted
Missing screenshots documentation
1 parent fb661f4 commit be05ef2

File tree

3 files changed

+11
-0
lines changed

3 files changed

+11
-0
lines changed
18.5 KB
Loading
254 Bytes
Loading

docs/smartui-cli-git-branching.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -312,6 +312,17 @@ $ npx smartui --config .smartui.json exec -- <Execution command>
312312

313313
<img loading="lazy" src={require('../assets/images/smart-visual-testing/git-baseline-non-baseline.webp').default} alt="Smart Visual Testing" width="1600" height="803" className="doc_img"/>
314314

315+
### Handling Builds with Missing Screenshots
316+
317+
When a build is executed in the same branch as the **Baseline Branch**, SmartUI will compare it against the latest approved baseline build. If some screenshots (or variants) that were present in the baseline are missing from the current build, a `Missing Screenshots` warning <img loading="lazy" src={require('../assets/images/smart-visual-testing/missing-ss/Validation.webp').default} alt="Smart Visual Testing" className="doc_img"/> will be displayed.
318+
<img loading="lazy" src={require('../assets/images/smart-visual-testing/missing-ss/Tooltip-missing.webp').default} alt="Smart Visual Testing" className="doc_img"/>
319+
320+
If this build with missing screenshots shows no visual changes compared to the baseline, it will be automatically approved. However, SmartUI will mark it as an `Incomplete` build and will not set it as a new baseline.
321+
322+
For builds with missing screenshots that do contain visual changes, you can manually approve them to set them as a new baseline if desired.
323+
324+
> **Note**: If a build contains any new screenshots that weren't present in the baseline, SmartUI interprets this as an intentional test case modification. In such cases, the `Missing Screenshots` tooltip will not be displayed, even if some screenshots from the baseline are missing.
325+
315326
### Auto Updating **Baseline** build for the **Baseline** branch
316327

317328
In this workflow, once all the `Changes Found` are approved by the `approver` for the screenshots in the **Baseline** branch's **Non-Baseline** build then the `latest` approved **Baseline Branch** build will be updated to the `Baseline`.

0 commit comments

Comments
 (0)