Feature Requests
297 results found
-
Update CodeLens test stats
In Visual Studio 2015, Code Lens shows me 0 passing tests, while NCrunch shows me all green markers.
Maybe it is possible for NCrunch to update the CodeLens test statistics.59 votes -
Filter to show running tests.
Hi, I'd like to have a new filter option along side the "show passing/failing/unexecuted/ignored tests" buttons which would allow me to "show running tests". My use case would be to have show enabled for failing, unexecuted, and running tests -- so I can more clearly see what NCrunch is up to at any given moment.
4 votes -
44 votes
-
ternary coverage
Increase resolution of coverage so that a ternary expression shows code coverage if one branch is not covered. (Otherwise my team is going to make me always use 8-line ifs instead of 1-line ternaries just so we can see code coverage completely :'( )
25 votes -
Option to run all test in current .cs file
I would be nice if I could tell NCrunch to run all tests in the current file.
Often related tests are implemented in the same .cs file. Some of the projects I work on are too large to leave ncrunch running all the time, so an option to just run all tests in a certain file would be really helpful.
5 votes -
License server - Show client version
On the license management page, show the client version for each line. This way I know who should update their clients.
3 votes -
NCrunch Console Tools provide TeamCity Code Coverage Stats
You can check TeamCity documentation here: https://confluence.jetbrains.com/display/TCD9/Custom+Chart#CustomChart-CustomBuildMetrics
CodeCoverageB Block-level code coverage %
•CodeCoverageC Class-level code coverage %
•CodeCoverageL Line-level code coverage %
•CodeCoverageM Method-level code coverage %
•CodeCoverageAbsLCovered The number of covered lines int
•CodeCoverageAbsMCovered The number of covered methods int
•CodeCoverageAbsCCovered The number of covered classes int
•CodeCoverageAbsLTotal The total number of lines int
•CodeCoverageAbsMTotal The total number of methods int
•CodeCoverageAbsCTotal The total number of classes int
31 votes -
Add button to enable/disable word wrap in test output window
The test output window currently wraps text which can make it difficult to read stack traces. An option to disable word wrap would be helpful, especially if it could be toggled via a button on the window itself.
8 votes -
Hide non test projects in the NCrunch Tests window
I typically leave the 'Show Passing Tests' filter enabled. However, when it is enabled, non-test projects also show up in the list with a check next to them. It would be good if the non-test projects would not show up at all in the tests view since there are no tests in them.
6 votes -
Native support for xUnit Collection attributes
Currently xUnit Collection attributes are not prohibiting nCrunch from running tests inside one collection in parallel. So developers require to decorate old tests with nCrunch-related attributes for those test not to be executed in parallel.
8 votes -
Color the console output
I really like the idea of separation of console outputs by test. But, the problem is, that with more logs the output becomes cluttered. There is an excellent plugin for Visual Studio called VSColorOuput that allows to specify regular expressions to color the console output in the output window.
Would you consider:
1. Add similar coloring preferences to console output
or
2. Output console to the output window, as requested in another feature request?4 votes -
Enable real time output of the test being run in "NCrunch Tests" window
It would be nice to have real-time or at least "refreshed" every 5-10 seconds "Test output" console in NCrunch Tests" window.
Right now the output is provided once test is completed, but it would be useful to have some kind of "refresh every N seconds" option for integration tests. They might take minutes to run, and sometimes it is extremely useful to see output in real time - either to kill the test or to see what's going on.
7 votes -
Improve hover-over hints on tests indicators/icons in 'NCrunch Tests' window
Oh boy, we still have absolutely no idea what do some icons mean. Really.
All these alerts icons on the test/assembly row, then green or red clocks, then green question marks. That IS so much puzzling. Seems we lived in VS space too much, at least it was simple - not run, run and pass/failed :)
Please add hints on hover-over providing an explanation and suggestion on what is going on with the current test or whole test set.
5 votes -
Mark tests using TestCaseSource as failed if an error in the method providing the TestCaseData fails
Currently an NUnit test that uses a TestCaseSource attribute to provide the data will not show up at all if the method providing the TestCaseSource data has an exception.
I often end up resorting to Resharper to run the offending test to find out what is going on.
It would be nice if the tests that are failing because their TestCaseSource is not running can show up as failed tests the same way that they do in Resharper.
5 votes -
Configurable list of custom ItemGroups to be copied over to workspace
More details - http://forum.ncrunch.net/yaf_postsm7334_Custom-ItemGroups-to-be-copied-over-to-workspace.aspx#post7334
The scenario is coming up with some shared logic to be used by other teams. They have the freedom to add build targets, so list of custom items used isn't fixed.
Currently NCrunch just copies over None or Content or Compile items. Having a configurable list of such items will help avoiding workarounds like adding the item twice.
8 votes -
Separate test output to separate dockable window
I sometimes work from home with 1 monitor and at work with 3 monitors. I also tend to like having test output in a less "important" place than the tests themselves.
With vstudio2015 the split setting (bottom or right) is not restored via the windows layout feature.
if test output was a separate window I can choose to place/dock it wherever I like (and also restore/save its position).2 votes -
Option to Build and Start Running Test Only on File Saves
It would helpful to have an option where NCrunch does not start building the project and running tests until after I save the file. We've had some issues with this in a project I was on that had several thousand unit tests. This would be similar to the way Karma's auto-file watcher works for JavaScript unit testing.
I'm aware of the sliding building delay - and it can help - but I feel it'd be better to just provide an option to not start processing until I save a file.
45 votes -
Pause instead of disable enable
I would love to just pause ncrunch at times instead of enabling and disabling which causes the solution to be rescanned again.
45 votes -
Offer a VS toolbar to make switching between engine modes quicker (and visible)
NCrunch should offer a VS toolbar to make switching between engine modes quicker (and visible). It's an often-used function and is tedious to do it through the menu.
3 votes -
Pause while nuget is installing or updating packages
NCRunch should pause while NuGet is installing or updating packages. There is no good reason to run tons of tests hogging most of the workstation performance while the solution is in an inconsistent and temporary state. Ncrunch running tests severely impacts the time it takes updates and installs to run.
PS: Resharper does this so I know it's possible :)
104 votes
- Don't see your idea?