Feature Requests
-
Earlier Support for .Net 5.0
Currently, NCrunch supports up to .Net Core 3.1
.Net 5 is on "5.0.0-preview.7" (2020-07-21) now and will be released for 1st November.
My leading role leads me to develop often en preview and it has a burden to switch OFF NCrunch for those projets (when preview .Net Core 3 was the same burden).
My question is when the support is planned to be? And Can, principally can you change your workflow to have "Earlier support" for the new versions?
Thank you,
Christian P. Gyssels
MCT1 vote -
Support build of Azure functions
Azure functions are becoming more and more used. Unfortunatly NCrunch is not compatible with them. What's the plan to support them ?
We wanted to give all developers on my company an NCrunch licence but we all add some Azure functions to our projects, so people instead use Continuous Testing from Jetbrains. It does the work, but NCrunch is clearly ahead. Hope it will be supported soon.
44 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 -
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…
1 vote -
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 -
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 -
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.
5 votes -
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 -
Add the ability to run a test fixture manually
It's easy and convenient to run an individual test manually by using the markers in the source, but there's no marker for running a test fixture (class with multiple tests in it). It would be nice if a dot were added for the fixture too.
1 vote -
Update or replace the NCrunch Forum software
The software used for the NCrunch Forum (forum.ncrunch.net) is really terrible for this day and age.
I tried to search for a DPI issue, and it griped at me for trying to search for fewer than four characters.
I tried to upload an image to show the DPI issue I was having, and it wanted me to give the URL of the image.
I'm sure this forum software was fine, at least better than nothing, back when NCrunch first came out, but just like NCrunch has improved over time, so has online forum software, and it seems like time to…
3 votes -
Allow more flexibility in test and hierarchy display
Currently there are six hard-coded ways to display tests in the NCrunch Tests window.
My proposal is that in place of this hard-coded list, there be a way to specifically configure what I want to see:
- Category (on/off)
- Project (on/off)
- Namespaces (one level per dot, or all grouped in one level, or none)
- Fixture (on/off)
- Test (full namespace.class.name / just method name)
Usually except for large projects I'd prefer to just show the test name, but currently there's no way to do that. "Test" view shows namespace.class.testname.
3 votes -
Add function to attach to a process by PID
I have a process that is being launched during the run of a test that I need to attach to. The current workflow of manually attaching to the test is slow and irritating. I believe since ncrunch is running as a VS extension ncrunch could provide a function to attach to a particular process by PID.
Sample code that implements this feature, with MIT license:
https://gist.github.com/xavierzwirtz/bd3dfcb5be4a0466cd4c106cc92f223e1 vote -
instrument C#.Net webapi server deployed on Microsoft Azure Service Fabric Cluster so as to get code coverage for the same
Need to be able to instrument C#.Net webapi server deployed on Microsoft Azure Service Fabric Cluster? I am looking to get code coverage for the same, for the integration tests that are running against a Webapi server deployed on the SF host.
1 vote -
Save the Timeline report every 10 minutes
Save the Timeline report every 10 minutes in order to keep the history of a whole work session (a few hours). I could make visual reports based on the xml file.
I would need this for the training / coaching I do with team that are learning TDD.
I want to show them how NCrunch can be used to improve their practice and reduce their feedback loops. I don't know any other tool that could do it for Visual Studio and it would provide precious information.
We could even make it a game/competition with clear number objectives!1 vote -
Support Inline Code Coverage in .razor Tests
NCrunch supports crunching xUnit tests defined in an @code block of a razor file. It would be great if automatic inline code coverage were supported for those tests.
1 vote -
Support Visual Studio 2019 Solution Filters
With 3.25 NCrunch builds and test the complete solution even if a Solution filter is used. This is one side a good thing, so that if i break something in a filtered project, this will be detected pretty quickly.
But it may be nice in some more complicated case, only run and build the projects which are in the filter. Because the filter is used to explizit not build and test some projects.
4 votes -
Possibility to turn off 'Churn...' when 'Show coverage on selected test only' is on
When you activate 'Show coverage on selected test only' while at the same time having 'Churn selected test until it fails' on, there is only a popup dialogue for turning off the 'Show coverage on selected test only'. It's probably more relevant to stop churning than to show coverage of all the tests in that particular situation, so It would be nice if the dialogue [also] offered the possibility to cancel the churning session.
1 vote -
Allow to exclude/include files for "Autodetect Nuget build dependencies"
The documentation (https://www.ncrunch.net/documentation/referenceproject-configurationautodetect-nuget-build-dependencies) describes that NCrunch is able to auto-detect NuGet package references.
It also states that it may happen that NCrunch workspaces might bloat significantly.
At least to work around some limitations it would be nice to have a filter that either excludes or includes specific files.
For example, I would like to exclude the .nupkg files and the .xml (documentation) files. In my specific scenario that would reduce the "bloat" from 16MB to 4MB as now I only include the DLLs I actually need.
1 vote -
Detect impacted tests when assembly attributes change that impact test running
With NUnit 3 I added [assembly:Apartment(ApartmentState.STA)] as an assembly-level attribute, thus applying to all tests in that assembly. Yet, NCrunch doesn't consider that for impacted tests. There are possibly also other assembly attributes that could impact all tests.
1 vote
- Don't see your idea?