Add Snapshot Evidence in Scenario Editor

Add Snapshot Evidence in Scenario Editor

IfThis page replaces old Designer 2.0 wording with current Scenario Editor guidance. Add snapshot evidence when a screenshot or captured state will help diagnose a failure or prove an important business checkpoint.

When snapshots help

• Before and after a critical action.
• At the userfirst wantsmeaningful tofailure savepoint.
• When validating layout, displayed data, or a snapshotconfirmation forpage.
• When atroubleshooting specificintermittent step,behavior thenacross abrowsers manualor Test Nodes.

Good practices

1. Name the step needsclearly to be added right after the target step.
2. Right click the step, for which you want to take a snapshot and select 'Add a new step below'

For this new line, select the Action value of 'htmlSnapshot'. The accessor and value fields should be blank. Note that if you would like snapshots of 2 different steps, you would need to add an 'htmlSnapshot' entry after each one of those. After running the script,so the snapshot is savedeasy to thisfind folder:in <AIQ>\sahi\userdata\logs\playback\imagesoutput.Capture only useful checkpoints; too many snapshots make analysis noisy.Keep sensitive customer data out of screenshots when possible.Attach execution output to the related defect or maintenance note.