How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Is there an easier way to re-test?

calendar_today October 30, 2026 person @Kalpana_Qaximus domain smartbear
Hi bestekov, you’re not using it wrongly, and the history problem is fixable. In the Test Player, Start a New Test Execution archives the previous result rather than overwriting it. The fail stays visible under archived executions at the bottom of the player: Rerun Tests and History of Test Execution Results Zephyr Documentation Defects linked to an execution also list it under Impacted Test Executions : Traceability in Test Executions Zephyr Documentation A lightweight workflow some teams use: When the defect is resolved, the verifier opens the cycle from the Test Cycles view, not the sta
open_in_new Read original post