You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see below, the Engine Team has a lot of work to do! We're a small team of volunteers and we welcome new members who want to help on any of our projects. If you are just starting, we'll guide you as you learn about our projects. If you have extensive experience, we can probably find a few challenges for you. Contact @CharliePoole or comment on this issue if you would like to join us.
What We Support
The NUnit Engine is the main component we support. The engine is used by almost all NUnit runners to load and run tests. It's a crucial bit of software, although somewhat invisible to the average user by design. The engine basically decides how and where to run your NUnit tests.
Along with the engine, we maintain the NUnit3 Console Runner. This was once the primary runner used to execute NUnit tests. Nowadays, most developers run their tests on the desktop in other ways but the console runner still has a significant place in the CI environment. In addition, it plays a valuable role in testing the engine itself and its code serves as a benchmark implementation for the development of any NUnit runner.
The engine team also maintains a number of separately built and installed Engine Extensions:
The NUnit Project Loader, which allows use of projects of type .nunit.
The VS Project Loader, which allows use of VS projects and solutions.
The NUnit V2 Result Writer, which creates output using the NUnit V2 format.
The NUnit V2 Framework Driver, which allows loading and running NUnit V2 tests.
Packages We Maintain
NuGet
NUnit.ConsoleRunner
NUnit.ConsoleRunner.NetCore
NUnit.Console
NUnit.Engine
NUnit.Engine.Api
NUnit.Extension.NUnitProjectLoader
NUnit.Extension.VSProjectLoader
NUnit.Extensino.NUnitV2ResultWriter
NUnit.Extension.NUnitV2Driver
Chocolatey.Framework.
nunit-console-runner
nunit-extension-nunit-project-loader
nunit-extension-vs-project-loader
nunit-extension-nunit-v2-result-writer
nunit-extension-nunit-v2-driver
MSI
NUnit.Console
Zip
NUnit.Console.Zip
The text was updated successfully, but these errors were encountered:
I'm a little late replying, but have kept this in my inbox until I could.
I've been intending and wanting to get more involved in the engine for a while now, however the main thing keeping me from it has been a lack of spare time. Hopefully over the coming months things will free up a bit and I'll be able to contribute. 🙂
As you can see below, the Engine Team has a lot of work to do! We're a small team of volunteers and we welcome new members who want to help on any of our projects. If you are just starting, we'll guide you as you learn about our projects. If you have extensive experience, we can probably find a few challenges for you. Contact @CharliePoole or comment on this issue if you would like to join us.
What We Support
The NUnit Engine is the main component we support. The engine is used by almost all NUnit runners to load and run tests. It's a crucial bit of software, although somewhat invisible to the average user by design. The engine basically decides how and where to run your NUnit tests.
Along with the engine, we maintain the NUnit3 Console Runner. This was once the primary runner used to execute NUnit tests. Nowadays, most developers run their tests on the desktop in other ways but the console runner still has a significant place in the CI environment. In addition, it plays a valuable role in testing the engine itself and its code serves as a benchmark implementation for the development of any NUnit runner.
The engine team also maintains a number of separately built and installed Engine Extensions:
.nunit
.Packages We Maintain
NuGet
Chocolatey.Framework.
MSI
Zip
The text was updated successfully, but these errors were encountered: