Feature Requests
298 results found
-
Scroll wheel zoom For NCrunch Windows
It would be nice to be able to use the scroll wheel to zoom in/out when in a NCrunch window.
1 vote -
Churn Mode - More fine grained statistics for test columns
When running churn mode I am interested in "Total test executions" i,.e. how many time test has been run in current churn mode, and "Total execution time" i.e. how long the churn mode has been going on (i.e. has it spent 1 minute or 30 minutes).
This so I know, when I decide cancel, that I ran it for e.g. 10 000 iterations and/or in 10 minutes so next time I want to "churn it" I get a hint how long I need to churn it .
2 votes -
In Tests window, include analyze time in "Last execution time" for test projects
For test projects, the "Last execution time" seems to contain the build time, where "Cumulative Build time" (I assume) aggregates these figures.
Say I have some projects with a build time of 20s, and analyze time of 30s before any test is run, I would like build+analyze time as a column, so I can spot test projects being overall bottlenecks.
Since analyze time is part of my "sit and wait" period, I get a better overview of which projects are bottle necks if these durations are inccluded in metrics, and can tell which projects I need to split into smaller…1 vote -
Goto TestCaseSourceAttribute's source from Tests window.
I would be nice if it was possible to opt-in to change behavior of the context menu "Go to selected test" in that way:
With NUnit, one can write:
public static IEnumerable<TestCaseData> MyTestCaseSourceMethodName()
{
// return test cases...
}[TestCaseSource("MyTestCaseSourceMethodName")]
public void MyTest(int someArgument)
{
// do test...
}The test case factory method can be an separate (static) class.
In my case, I have a test with several dozens of test cases.When a test fails, I can easily go to the failing test implementation, but I cannot easily find the culprit test case.
2 votes -
Allow for easy command-line installation (e.g. Chocolatey)
Our development machines are built via PowerShell script, which is a very flexible and maintainable way of scaling to many developers. The scripts rely heavily on Chocolatey packages to install software, but unfortunately the unofficial Chocolatey package for the NCrunch Visual Studio plugin is not reliably updated and does not cope well with upgrades. Also, there is no command-line NCrunch package.
Given that Chocolatey packages are relatively simple wrappers around the existing product installers, it would be great if you could work with the existing package maintainer to improve the existing package, and create a package for the command-line application.
6 votes -
Time limit option for Churn mode
I would like to be able to Churn tests for x seconds/minutes and if it hasn't failed within that time stop churning.
This so after I have fixed a failing test, which I know fails in churn mode within x seconds, I don't want to run "Churn until it fails" but rather set a time period I know should be sufficient to reproduce it.
1 vote -
Don't show "NCrunch Client Disabled" as an error in red
When I try to connect to an NCrunch grid node and get "NCrunch Client DIsabled" in red text, my first impulse is to troubleshoot. Is it a firewall problem? Bad password? Something else?
Then it clicks...client. I don't have NCrunch enabled in my current Visual Studio solution (or maybe I don't even have a solution loaded yet).
Well, obviously NCrunch won't send anything to the node if there's nothing to send. This isn't really an error, per se, so I don't think NCrunch should show the message in red in this case.
1 vote -
Toolbar button for "Run Selected Test(s) In Existing Process"
I often have failing tests in my test window that I want to re-run in existing process (if there is one), e.g. when modifying database the tests are hitting.
Today I must go via RMB->Advanced, rather than just clicking a toolbar button (similar what exists with "run test(s) in new process".2 votes -
History of work session
I'd like to be able to see the history of my work session, meaning at the end of the day I'd like to see visually when my code was compiling, when my tests were all green.
The purpose is to be able to identify if I spend a lot of time in those states and try to reduce that time.
It would be useful for self-improvement or coaching.1 vote -
Extend line hit markers to include hit count and first hit order
Two existing requests want hit count:
, but I think that it would also be great if you could include a first hit order, then from a glance you could see the execution steps through the code (probably by thread in case multiple threads are used) and determine if line A was executed before line B
1 vote -
Select current file in Metrics window
I would like to select the file I have opened in visual studio, in the metrics window, so I don't manually have to find it by clicking through the project structure.
Background: I have a build failing if metrics is below a threshold for specific files. When this build fails I get a list of file names. Then it is tedious for me to fix this "file by file" since I have no quick way of selecting current file in metrics window to verify my fixes.
2 votes -
Allow an ignored test to be run manually
When a test is ignored either allow it to be run manually or disable the "Run selected test in new task runner process" in the popup menu in "NCrunch Tests" window.
Right now you can click the item in the popup menu but the test is not run.
Preferably I would rather be able to run the test on demand.3 votes -
Add predefined keyboard shortucts to switch between engine modes or make it possible to configure them manually.
As per title. Now doing it with mouse it way too inconvenient.
2 votes -
Configuration option to completely remove the failing build message
The message below is not necessary for users familiar with your product:
NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues
It has 2 drawbacks:
1) It contains a url which is easy to hit as there is no space between this url and the url for the first error in the build.
2) It takes up screen space.
So, a configuration option in General Settings to turn this off would be good. For those who wish to see the message, add a line between it and the first error message to…
1 vote -
Show what it the currect engine mode on "NCrunch Test" screen or maybe via some icon in the VS status bar.
Why?
I often switch between modes like this:
Run all tests automatically -> Run all tests manually or Run pinned test automatically -> Run all tests automatically
This is due to make sure NCrunch does not get into the way by running tests that at the moment are doing more harm than good.1 vote -
A more obvious colour of the coverage markers to show a build error
When working in code, test or otherwise I would like more obvious feedback for when a build has failed as I often mistake the dull green of a previously passing test with a failed build for the normal passing green.
1 vote -
Gated Check In Support
It would be great if Ncrunch provided an optional gate for check-ins when there are failing unit tests. Check-ins to version control systems would fail and display failing tests.
This would be helpful for long-running unit test builds, so that the work could be offloaded from a central build server to incremental runs on everyone's dev machine.
1 vote -
Shortcut to run only failed tests
Sometime I fix an issue for a failing test where NCrunch cannot detect the test is impacted.
Instead of running all pinned tests I would like to bind a shortcut to only run failing tests (Similar to vstudio's TestExplorer.RunFailedTests) to verify the fix quickly.1 vote -
"first failing test"
I suggest you include the option to highlight the first failing test in the "NCrunch Tests" window and display the details.
Right now when there are no tests failing and a test fails, I have to click on it in order to see the details of why.
Having it automatically show the details would be very helpful and save a few clicks.
6 votes -
Test Coverage Analysis by Specific Test Class
I suggest to make possible to change the way code coverage is calculated.
While I am developing I do not do much end-to-end testing. What I do is purely unit testing as part of my TDD process. I would like to have the code coverage calculated class by test class.
Example case: Class "Car" being tested by class "CarUnitTests". I would like to have the code coverage of class "Car" being calculated exclusively by the tests present in "CarUnitTests".1 vote
- Don't see your idea?