-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volunteers Wanted for the NUnit Engine Team #1221
Comments
I'm a little late replying, but have kept this in my inbox until I could. |
If you're able, that would be great! |
I'm very late, but I am willing to learn and contribute. |
@manikumarnune123 So am I, I'm afraid! Still interested? @stevenaw If things have freed up, take a look at the 3.19 milestone and let me know if anything is of interest. |
Thank you for following up @CharliePoole |
I will continue to keep an eye on things, of course, and will pick up an item if time permits. 😃 |
Fair enough. If you can find any time now, cast an eye on the 3.19 milestone. I decided to be a bit more structured and spell out the content in advance, with priorities. I'd appreciate any general comments (what's missing for example) as well as internal comments, esp. on those things labeled as needing discussion. I appreciate the thanks. :-) |
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.
Zip
The text was updated successfully, but these errors were encountered: