[feature request] release a OpenTelemetry.Extensions.TestFX package

[thompson-tomo]

Component

None

Is your feature request related to a problem?

I want to have the traces & metrics generated by my application when running unit tests recorded just like in production with the results visible in the same tools.

What is the expected behavior?

New package is available which enables open telemetry to be add to the test project with minimal effort on test projects.

• ITestFramework.CreateTestSessionAsync implemented to start the activity for the test suite with the necessary tags
• ITestFramework.CloseTestSessionAsync implemented to stop the activity for the test suite
• ITestFramework.ExecuteRequestAsync implemented to set the test result as passed, any other appropriate tags & end it when IData is PassedTestNodeStateProperty
• ITestFramework.ExecuteRequestAsync implemented to set the test result as failed, any other appropriate tags & end it when IData is FailedTestNodeStateProperty
• ITestFramework.ExecuteRequestAsync implemented to set the test result as skipped, any other appropriate tags & end it when IData is SkippedTestNodeStateProperty
• ITestFramework.ExecuteRequestAsync implemented to create a new span with the appropriate tags when IData is InProgressTestNodeStateProperty

Which alternative solutions or features have you considered?

Manually instrument it within my projects.

Additional context

https://learn.microsoft.com/en-au/dotnet/core/testing/microsoft-testing-platform-intro

• Attributes for repository semantic-conventions#2329
• Capturing of test failures as events semantic-conventions#1141

[martincostello]

We discussed this in the CI/CD SIG meeting this week - I was going to look into creating a prototype once phase 2 kicks off.

[thompson-tomo]

Thanks for that @martincostello I think from a users perspective if the interface was identical or as close as possible to OpenTelemetry.Extensions.Hosting that would be best. That way we can have seperate resource package to add the git information and any other desired info.

Note I have just linked 2 issues to extend the attributes so that desired info can be captured.

[thompson-tomo]

After thinking about it some more I have come across a number of other gaps hence have raised the following:

• Add namespace for the library being used semantic-conventions#2339
• Sub namespace for runtime within app semantic-conventions#2341
• App details lack key info semantic-conventions#2346
  Metrics for tests semantic-conventions#2350