Conversation
docs(skills): describe how lifecycle hook failures are reported A throwing #[AfterTest] replaced the test result with an Aborted pipeline failure, so the test's own failure disappeared from the report, and a throwing #[BeforeTest] skipped every #[AfterTest]. Hook failures are now test errors, teardown always runs, and throwables that do not become the test's failure go to the stderr channel. Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔍 What was changed
#[BeforeTest]stops the remaining setup hooks and the test body. The test isErrorwith that exception, notAborted.#[AfterTest]hooks always run: after a failed setup too, and each one even when a previous one threw.Error. A failed test keeps its own failure.stderrchannel.Why?
A failing
#[AfterTest]replaced the test result with aPipelineFailure, so a red test showed only the teardown error and its real failure was lost.Checklist
Documentation
testo-write-testsskill describes how hook failures are reported.