CharliePoole
CharliePoole
We should verify that any new console / engine build works with the latest releases of each extension we support. Currently, we only test the NUnitProjectLoader extension.
The agent is present in some branches but has never been released. Resolving this may simply involve making sure the right commits are present in main and go to release...
Currently, we assume that every entry in the file, once blank lines and comments are removed, is either a pattern or a valid path. Patterns are expanded to paths while...
UPDATED to provide a simple repro ### Prerequisites - [X] I have written a descriptive issue title - [X] I have searched [issues](https://github.com/cake-build/cake/issues) to ensure it has not already been...
Currently, NUnit supports a number of generic constraints that define the type of the tested expression at compile time (if they succeed): `Is.TypeOf()`, `Is.AssignableTo()`, and `Is.InstanceOf()`. (Note that `Is.AssignableFrom()` is...
Currently, those tests are commented out. Should be disabled for GH Actions and run locally as an initial fix. Longer term, we should figure out how to run them...
The framework makes an attempt to clean up test event reports before sending them. However, it's letting `'\uffff'` through. This lead to issue nunit/nunit-console#1469, which I am fixing by changing...
Each of our console packages is distributed with an addins file in the engine directory. The file is used to find extensions that use our default naming pattern in one...
BACKGROUND When the runner or engine encounters a file name for which we can't run tests, we could obviously just throw an exception and terminate. That's acceptable if the invalid...
The help screen is getting very long. While it's possible to send the output to `more`, that loses the color display because of how our implementation of `ColorConsole` works. So...