TUnit test framework

[AdaskoTheBeAsT]

🤔 What's changed?

Added implementation of TUnit Provider

⚡️ What's your motivation?

This is completelly new feature for test framework based on source generation

🏷️ What kind of change is this?

• ⚡ New feature (non-breaking change which adds new behaviour)

♻️ Anything particular you want feedback on?

I am not sure if this is proper way of creating plugin - I tried to adjust all the stuff similar to NUnit xUnit and MSTest implementation.

📋 Checklist:

• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

---

This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

[thomhurst]

Will this work? Tunit uses source generators and so does reqnroll. Source generated code can't see other source generated code so it may not be able to generate test cases: https://github.com/orgs/reqnroll/discussions/418

[AdaskoTheBeAsT]

it is beginning but apparently yes

[thomhurst]

Nice work 😁

[gasparnagy]

@AdaskoTheBeAsT This looks pretty good so far. 🤘

One small comment: traditionally the unit test provider classes have been added to the UnitTestProvider folder of the generator project, but this was because at that time we did not have a plugin system. In your case, you can (and you should IMHO) put your unit test provider class to the generator plugin project and add move the registration to the plugin class like we do for example here.

(In principle we should have moved the NUnit/xUnit/MsTest stuff as well to their plugins, just we haven't done that yet.)

[AdaskoTheBeAsT]

@gasparnagy thanks for feedback I moved that registration to plugin