Joseph Musser

Some folks will be interested in doing that, so that would be a valuable description. I wouldn't necessarily call out `[Values]` in particular.

Yes, I tried once or twice and ran into backwards compatibility issues. The biggest learning from my own experiences outside NUnit is that fluent APIs are a lot of work,...

@CharliePoole I'm generally interested. A month ago I tried again to retrofit true-async assertions and I have some thoughts on that too. Is that something you're including?

The page we have for this is out of date. https://github.com/nunit/docs/wiki/NUnitLite-Options I just tried to use `--exclude=SomeCategory`.

How odd! I edited as part of a wiki-wide formatting sweep on a local clone. But today I got there from a google search: 

We could provide a `TestContext.Exit()` in a similar vein to `Environment.Exit()` and `Application.Exit()` for those that would rather lose any remaining information in an effort to see the previously-completed results...

I mean, I wouldn't be hard to persuade, but it would have to be popular with the @nunit/framework-team (or highly demanded) before I felt comfortable pushing for an NUnit `.Exit()`.

@nunit/framework-team Would the best approach be to compare current framework code to the docs, or maybe to even come up with an XSD in the framework repo?

@mikkelbu I have some extra time today. Was anyone else hoping to tackle it?

😆 Okay. Now I'm confused. I would have thought that the XML was driven totally by the framework, not the engine. Where am I looking to find the source of...