Paul "Code Grump" Turner

A few thoughts from doing this work: 1. Due to how they're loaded into Roslyn, we ideally want a single package that contains all the analysers and code-generators with as...

> Isn't there a .NET framework mismatch then? If I compile my test assembly to .NET 6 on .NET 8 SDK, will the generator be running in .NET 6 or...

Next steps: - Going to look at replicating the output of the current generator for NUnit+CSharp projects. - Will add add some tests to validate the behaviour. - Will begin...

@gasparnagy The only complication would be determining the desired output. If you can give me an desired output for an example input, I can drop it onto a test and...

I've added an implementation of an MSTest generator using the example provided as a specification. I made a few alterations to target text, but kept it as close as possible,...

Forgot to mention: I put in a test-generator selector mechanism that looks for test framework assemblies to determine which framework is being used. We could reasonably put all the code...

> What should be the next steps? I think feature-wise the POC is complete. Do you have anything else you would like to experiment with before we start planning how...

The example provided by MSTest includes a `TestContext` argument. Importantly it contains a "Properties" bag that can be leveraged to route information into all tests.

I am thinking about execution in terms of scopes, analogous to how a DI container scopes resources: if you were to define a singleton at the Test Run scope, that...

You are correct, I think the "Test Thread" container _is_ unique to Reqnroll's architecture, not easily married to any of the test frameworks. Since the advent of Task in .Net...