[Feature]: Add support for test attachments

[DaRosenberg]

Problem Statement

We recently started migration of our whole test suite from NUnit to TUnit. We quickly realized there might be a blocker for us: we make extensive use of test attachments, particularly in integration tests. For us they are indispensable for figuring out why integration tests fail.

In NUnit we do TestContext.AddTestAttachment(filePath, name) but I cannot find anything in the TUnit TestContext that looks like an equivalent, nor can I find any mention of attachments or artifacts in the docs.

As far as I can tell it was added to MTP 1.7 back in March.

Is this already possible in TUnit and I've just not looked in the right place? If not, any chance we could get this added to TUnit?

Proposed Solution

I would like TUnit to support test attachments through a mechanism similar to that of NUnit.

Alternatives Considered

No response

Feature Category

Test Output / Reporting

How important is this feature to you?

Critical - blocking my adoption/usage of TUnit

Additional Context

No response

Contribution

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

[thomhurst]

Heya @DaRosenberg - Is TestContext.Current.Output.AttachArtifact(...) what you're looking for?

[DaRosenberg]

@thomhurst 😂 I saw that property in IntelliSense but assumed it was a stream! Thanks! And good shout to add it to the docs.

[DaRosenberg]

The ergonomics are a bit awkward through...

NUnit: TestContext.AddTestAttachment(filePath, "Diff")
TUnit: TestContext.Current.Output.AttachArtifact(new Artifact() { File = new FileInfo(filePath), DisplayName = "Diff" })

A convenience overload would be a very welcome addition, maybe something like:

TestContext.Current.Output.AttachArtifact(string filePath, string? displayName = null, string? description = null);