Feature Requests
-
Add support for custom MSTest V2 "custom" TestClass and TestMethod Attributes
MSTest suports overriding certain behavior in the TestClass and TestMethod attributes using inheritance.
This blogpost describes the pattern well: https://www.meziantou.net/mstest-v2-customize-test-execution.htmNcrunch currently does not discover tests with custom attributes as tests, so this customization is not available using NCrunch
3 votes -
Visual Studio 2022 Support
Add support for the preview versions of Visual Studio 2022. Really enjoying working with the VS Preview, but have to keep switching back to stable versions to get ncrunch results.
3 votesWe’re working on this one. The first preview of VS2022 has only just dropped, so we don’t have an ETA on this yet.
-
Show tests in the order they are run if Order attribute is used
If you use NUnit's Order attribute, you can specify an exact order (dependencies) for the tests to run, which also works with NCrunch:
https://docs.nunit.org/articles/nunit/writing-tests/attributes/order.html
In the NCrunch window, the tests are however always sorted alphabetically, which makes not much sense, given they are run in a different order. They are just hard to find then e.g.
It would be nice if you could order them non-alphabetically by order instead.1 vote -
Add suppport for triggering endless churn mode from console
Its common that the develop machine is turned of during the night so the endless churn mode doesn't get used as much as it should. We have like many others a dedicated build server and we would love to have the possibility to trigger a nightly build that churns the tests in the solution for a fixed period of time (a few hours or so) so we can gather all failing tests in the morning and make an attempt to fix these tests.
1 vote -
Add support for bUnit (Blazor Testing Library) Razor tests
Would be nice to run razor based unit tests so that I can use ncrunch while testing my Blazor applications. The link below is a report of what happens when I attempt this currently. I would be happy to help in any way that I can if this feature is picked up. Thanks again for the wonderful testing tool
https://forum.ncrunch.net/yaf_postst3093_bUnit--xUnit-Razor-tests-failing.aspx
2 votes -
Mark failed NUnit's TestCaseAttributes
It would be nice to mark failed NUint's TestCaseAttribute-s?
Otherwise it's hard to figure out what is failing.1 vote -
Creat A Simple API To Control NCrunch Execution and get Responses From It
A simple api like, start TEST blah blah ... and get the response whether success or failure, and the console output that is generated , just like in the NCrunch Tests window.
Also API to start, stop , restart NCrunch , and check current status.
I'd like to be able to build a simple tool so I can control test execution. :-)
Maybe NCrunch already has an object model we can tap into??
1 vote -
License server as docker image
We do not run virtual servers anymore in our company. Everything is running in k8s.
Therefore It would be great for us if you could provide us a way to run the server as a container.1 vote -
Allow sorting of tests in the test window by code order
Please add an option to allow sorting by natural code order in the test window. So the tests appear in the same order in the test window as they do in the source code file.
Tests are typically written in roughly increasing order of complexity and dependency - in general, I would almost always want to fix a test that appears first in a source file before those that appear after it.
Tests are also often (very) loosely grouped together by position in the file - related tests will be next to each other, and it would be helpful to…
3 votes -
configuration
NCrunch configuration.
When updating configuration for a solution with many projects, let me change more items before restarting crunch with the new config.
The problem is that I add a missing folder to support (yes this is a bad solution) a 80 project solution with many failing projects that every time I add a folder it starts again. I would like to add missing folder for each failing project before the result window closes.
My work around will be to write down the failing folders then update the configuration from that.
1 vote -
Stand-alone UI
I love NCrunch. I don't love Visual Studio. Working in VS is like running a big, fat, slow-turning oil tanker and it has started to make me more and more annoyed as time goes by. I have found myself working more and more with command line and VSCode.
So, I would like to be able to use NCrunch in that context. A plug-in for VSCode would be nice, but maybe another solution would be to have a completely stand-alone UI for NCrunch, so it can be run separately, but with about the same feature set as included in VS.
3 votes -
Add support for specialized excepted exception custom attributes in MSTest
If you decorate a unit test with the ExpectedExceptionAttribute in MSTest, it handles it correctly. However, if you derive from ExpectedExceptionBaseAttribute in your own custom attribute to make a more specialized implementation, NCrunch and Visual Studio disagree about whether the test passed.
1 vote -
Run pinned tests if there are any; run all tests otherwise
As the title indicates, I'd like an option to run only the tests I pin and if I unpin all tests, it should then run all of them.
1 vote -
Support runsettings TestRunParameters
My MsTest project has a simple .runsettings file like this:
<RunSettings> <TestRunParameters> <Parameter name="foo" value="bar" /> </TestRunParameters> </RunSettings>These parameters are supposed to be injected at runtime into all test classes TestContext property
public TestContext TestContext { get; set; }Then you can use that property like this:
[TestMethod] public void TestMethod1() { Assert.AreEqual("bar", TestContext.Properties["foo"].ToString()); }Unfortunately the this doesn't work when running NCrunch as the properties are not picked up. There doesn't seem to be a way to specify the path to the .runsettings file in NCrunch settings.
When running via Visual Studio or on Azure DevOps this works…
2 votes -
Integration Test Detection Metric
Some of the pitfalls of Integration tests are listed in the docs (https://www.ncrunch.net/documentation/guides_integration-testing) and identifying when they've been accidentally introduced into the test suite would be a nice feature.
An Integration Test Detection could be a metric or report that identified unit tests that are executing a large number of production code classes. In an ideal unit test the number would be 1, the class/system under test. For tests that are tightly coupled to other classes the number might grow quickly. These are problem areas that might need some design work to reduce the coupling or maybe just…
3 votes -
Provide visual hint that license has expired
My license expired a few days ago but I didn't realise until I happened to be looking at the version info for other reasons. I would suggest adding a small visual hint (perhaps in the Ncrunch tests window) to indicate that the license is about to expire or has expired.
1 vote -
Be able to run grid node on linux
Provide the ability to run a grid node on linux.
I mainly develop for dotnet core with CI being linux based and deploy exclusively on linux based environments (though I develop on Windows 10 as a personal preference).
I would be great if I could deploy grid node to linux local / cloud hosts.
7 votes -
Opt-in option for selection of which projects are monitored
Currently, the selection of which projects are built is opt-out. That is, all projects are monitored and built unless you set the "Ignore completely" flag explicitly on a project in your configuration.
It would be nice to have something that works more like building from the GUI or the command-line would: an opt-in feature.
In this proposed new mode of monitoring-selection, projects would still be monitored, built, and tested exactly as they are now. The only difference would be that all projects would be ignored completed and you would have to explicitly choose a project to be monitored. Obviously, any…
1 vote -
Do not count empty lines after exceptions as uncovered
Assert.Throws<Exception>(delegate
{
ThrowsAnException();
});If the method ThrowsAnException throws an exception, the last line "})" is marked as uncovered.
2 votes -
Treat unit and system tests differently
I've worked in a number of scenarios where we had a subset of tests which would be better classed as "system tests". I.e. they covered a large amount of system functionality and took a considerably amount of time to run (sometimes minutes). Running these as conventional unit tests under Ncrunch, triggered by every editor change is overkill but OTOH the Ncrunch UI is really nice and its ability to automatically run things is very helpful. It would be useful if these tests could be treated in a different way to normal units tests, e.g. only run on a scheduled basis…
4 votes
- Don't see your idea?