Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 13, 2025

Documentation used the deprecated direct context.Result property access instead of the current context.Execution.Result API, and incorrectly referenced TestStatus enum instead of TestState.

Changes

Updated four documentation files to use the correct API:

Before:

if (context.Result?.Status == TestStatus.Failed)
{
    await CaptureScreenshot(cancellationToken);
}

After:

if (context.Execution.Result?.State == TestState.Failed)
{
    await CaptureScreenshot(cancellationToken);
}

Files Modified

  • docs/docs/test-lifecycle/cleanup.md - After hook example
  • docs/docs/advanced/test-variants.md - Property-based testing shrinking pattern
  • docs/docs/advanced/extension-points.md - Event receiver examples (2 locations)
  • docs/docs/advanced/performance-best-practices.md - Test metrics tracking example

All documentation now correctly accesses test results via the ITestExecution interface as context.Execution.Result?.State.

Original prompt

This section details on the original issue you should resolve

<issue_title>Documentation: TestContext.Result?.Status == TestStatus.Failed should be context.Execution.Result?.State == TestState.Failed?</issue_title>
<issue_description>https://tunit.dev/docs/test-lifecycle/cleanup

Before

[After(Test)]
public async Task Cleanup(TestContext context, CancellationToken cancellationToken)
{
    // Access test results via context
    if (context.Result?.Status == TestStatus.Failed)
    {
        await CaptureScreenshot(cancellationToken);
    }
}

After

[After(Test)]
public async Task Cleanup(TestContext context, CancellationToken cancellationToken)
{
    // Access test results via context
   if (context.Execution.Result?.State == TestState.Failed)
    {
        await CaptureScreenshot(cancellationToken);
    }
}
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…ult to context.Execution.Result

Co-authored-by: thomhurst <[email protected]>
Copilot AI changed the title [WIP] Fix test context result status check in cleanup method Fix documentation: Update TestContext API from context.Result to context.Execution.Result Nov 13, 2025
Copilot AI requested a review from thomhurst November 13, 2025 19:29
Copilot finished work on behalf of thomhurst November 13, 2025 19:29
@thomhurst thomhurst marked this pull request as ready for review November 13, 2025 19:30
@thomhurst thomhurst merged commit 6328812 into main Nov 13, 2025
5 checks passed
@thomhurst thomhurst deleted the copilot/fix-test-context-status-check branch November 13, 2025 19:30
@suugbut
Copy link

suugbut commented Nov 13, 2025

https://tunit.dev/docs/test-lifecycle/test-context

if (TestContext.Current?.Result?.State == TestState.Failed)
{
    // Take a screenshot?
}

should be

if(TestContext.Current?.Execution.Result?.State == TestState.Failed)
{
    // Take a screenshot?
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation: TestContext.Result?.Status == TestStatus.Failed should be context.Execution.Result?.State == TestState.Failed?

3 participants