[Feature]: Multi step test execution with OTEL and Aspire (Gherkin - BDD style)

[AdrianoAE]

Problem Statement

We have very complex flows that require a lot of setup across many services and then check many services once the processing is over, in order to make the code maintainable we use the DependsOn, as a simple example:

SetupWiremock
SendServiceBusMessage [DependsOn: SetupWiremock]
VerifyWiremockWasCalled [DependsOn: SendServiceBusMessage]

Currently the report for the Class Timeline does not show the spans for the test methods (example) and would be good if the order of execution would match the order of the spans shown

Now for the problematic part with OTEL, even though I can verify while debugging that the OTEL headers are being sent in the ServiceBusMessage when sending from the test and forwarded all the way in the call chain, it never shows in the TUnit report, the traces are just lost.

The OTEL endpoints, etc. are injected in the services as per documentation, and the expectation is that they would show under the Send_message step since that's the one who actually triggers the processing. Also the traces are never sent to the Aspire dashboard as per documentation

Debugging screenshots:
TUnit Sending the message

Azure Function APP (running via Aspire integration)

The HTTP call the App does when the processing is done

TUnit verify step, I can check Wiremock that the request with the SendMessage TRACE-ID was made

Proposed Solution

• Have the traces properly propagate back to TUnit and shown under the report
• Traces proxied to Aspire dashboard as per docs

Alternatives Considered

No response

Feature Category

Test Execution / Lifecycle

How important is this feature to you?

Nice to have - would improve my experience

Additional Context

No response

Contribution

• I'm willing to submit a pull request for this feature

[thomhurst]

@AdrianoAE is it emitted under a different source? If so you'll have to instruct TUnit to listen to it like:

    [Before(TestDiscovery)]
    public static void Configure()
    {
        TUnitOpenTelemetry.Configure(builder => builder.AddSource("MySource"));
    }

[AdrianoAE]

Looking at the activity source when the HTTP call is made shows Microsoft.Azure.Functions.Worker

Adding it to the TUnitOpenTelemetry made no difference

[thomhurst]

Dang - I'll try and take a look later. Thanks for reporting

[thomhurst]

Might also chuck copilot at it in the meantime to see if it finds anything

[AdrianoAE]

When running the app normally and sensing a message, the main trace is with source Azure.Messaging.ServiceBus.ServiceBusProcessor, also tried adding it but did not work either

[thomhurst]

@AdrianoAE Can you locally try these nupkgs and report back?
https://github.com/thomhurst/TUnit/actions/runs/25492765020/artifacts/6854471864

[AdrianoAE]

Nothing changed, (still have the 2 Souces in the code), looking at what copilot did, it ignored the whole OTEL problem and the changes it did to have the spans under the class did not work, but the ordering is nice now 🙂

[thomhurst]

@AdrianoAE you're right - I got it to make some changes. These maybe look more promising - It's apparently performing OTel span linking which sounds more correct.

New test packages: https://github.com/thomhurst/TUnit/actions/runs/25499057781/artifacts/6857565202

[AdrianoAE]

@thomhurst Nothing changed