Log Specific Errors During Scenario Execution

Last reviewed: September 29, 2026
Use this article when a Scenario Editor test needs to capture targeted errors for debugging or reporting.
What changed in this article
Changed the vague title into an execution logging task.
Added guidance for capturing step context, input data, browser state, response details, and assertion messages.
Added caution to avoid logging secrets, tokens, passwords, or customer-sensitive payloads.
Validation workflow
Decide which error condition needs explicit logging and where it occurs in the scenario.
Log the minimum useful context: step name, data row, expected value, actual value, and relevant output.
Review execution output to confirm the log helps diagnose the failure without exposing sensitive data.
Review note: Added data-safety guidance so error logging is useful but not noisy or risky.
Last updated: September 29, 2026
If you have feedback on this topic, contact documentation@appvance.ai.