You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(evidence): expose collision-safe failure artifact records #152
Depends on #151: this follow-up should be reviewed and merged only after the supported runner-config/hook work in #151.
NativeProof's built-in failure capture still cannot give a reporter-neutral consumer the evidence files belonging to a failed test:
failureEvidenceName hashes only parent + title, so the same named test collides across spec files, projects, and retry attempts.
captureState intentionally returns page-source XML text, not the PNG/XML paths, and the generated afterTest hook does not expose those paths.
This leaves generic reporters unable to associate the exact files NativeProof actually saved without guessing filenames. #140 fixed sanitization/truncation collisions, but not this identity/association gap.
Acceptance criteria
Add a minimal config-level callback for built-in failure evidence; no Allure dependency and no new test DSL.
The callback receives a structured record identifying project, file, fullName, and retry attempt, plus the exact PNG/XML paths actually produced.
Failure filenames include the complete identity, so same-title tests differ across files, projects, and attempts.
Preserve the public captureState(prefix): Promise<string> API.
Preserve built-in default capture before the existing consumer afterTest hook.
Passing tests do not invoke the failure-evidence callback.
Capture failures do not report fictitious paths and do not replace the original test failure.
Activity
BenSheridanEdwards commentedon Sep 15, 2026
Implementation is open in #153, stacked explicitly on #151. It has not been merged or released.
feat(evidence): expose failure artifact records (#152)
feat(evidence): expose failure artifact records (#153)