Doc: Clarify TestContext lifecycle and hook execution order - #64867
Open
Rawal27 wants to merge 3 commits into
Open
Doc: Clarify TestContext lifecycle and hook execution order#64867Rawal27 wants to merge 3 commits into
Rawal27 wants to merge 3 commits into
Conversation
Collaborator
|
Review requested:
|
Signed-off-by: Rawal27 <obviouslykamal@gmail.com>
Rawal27
force-pushed
the
docs-test-context-lifecycle
branch
from
July 31, 2026 11:17
4d0fe06 to
2c89577
Compare
Signed-off-by: Rawal27 <obviouslykamal@gmail.com>
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
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.
Summary
Improve the
TestContextdocumentation by adding:TestContextinstance is created and how it relates to subtests.TestContextinstance.These additions make the
TestContextdocumentation easier to understand for users who are new to the test runner, while complementing the existing API reference without changing any behavior.Documentation changes
TestContext lifecycleExampleExecution orderNo functional changes.