Feature Requests
298 results found
-
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 -
Do not automatically perform a build if tests are set to run manually
We have some projects that are very expensive to build. Since I would like to see the output of the last test, I do not want to disable NCrunch completely, but the build engine keeps building the projects even when the tests are all set to run manually and I haven't yet started a test. I would like the option to defer the build until a test is scheduled for execution.
3 votes -
Display Reason for ignored tests
I use Nunit, with ExplicitAttribute(string reason) on TestFixture class.
The tests are correctly ignored but there no reason visible in NCrunch Tests window.It would be nice to have the reason, when I select an ignored test. Perhaps in Trace Output (which is empty for ignored tests).
3 votes -
Expose MSpec's [Subject] details in the tests window
MSpec uses a [Subject] attribute to nominate the unit-under-test and optionally allows a "concern" to be specified.
In R# these items appear in the test runner window as part of the test name, however in NCrunch there doesn't seem to be any way to get at this information, which is unfortunate.
There just seems to be a level of organization missing when working with MSpec tests. It would be really helpful to be able to group the tests either by the [Subject] attribute, or by the file name that the test is defined in.
3 votes -
Hits count on coverage marker circle
When I click on a coverage marker circle, a windows pops up with Test name and execution time information.
It would be nice to have also a third column indicating how much times the test hit the current line3 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 -
Provide a better filtering on 'Tests being excecuted right now' in 'NCrunch tests' window
With large amount of tests, say 500-1000, it is impossible to see what is going on right now - which tests are being executed.
NCrunch has a specific icon on that, but all such tests are spread across the 'NCrunch tests' window, so we have to scroll here and there to see where NCrunch is up to - which tests are being run right now.
It might not b an issue for unit tests, but integration tests take about 1-2 minutes each to execute, so sometimes it is not clear what's is going on.
Would be nice to have either…
3 votes -
Add host spot detection.
Add the ability to highlight risky code paths to help a developer focus their attention on un-covered code paths.
Hot spots should be defined by areas of high cyclomatic complexity and low test coverage similar to the functionality found in JetBrains dotCover.
3 votes -
Add progress bar to Metrics tree view
I would find the metrics tree view more useful if the code coverage % column had a progress bar in the background. The numbers are great of course, but a progress bar would be much easier to glance at, especially when looking at a large number of rows.
DotCover has a view that shows what I mean well: https://www.jetbrains.com/dotcover/features/img/dotcover-app.png
3 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 -
Implement Ctrl+A shortcut in NCrunch configuration grid
For the moment it's possible to select more than one project but only holding Ctrl key and clicking on each project.
3 votes -
Separate 'successfully completed' and 'failed tasks' in the Processing Queue window
The NCrunch Processing Queue window currently has 3 toggles:
- Pending tasks
- Tasks being processed
- Completed tasksThe last of these has both the successfully completed and the failed tasks. However, I find that confusing and inconsistent:
- The icon on the toggle button is a checkmark. The icon for successful tasks is a checkmark, while the icon for a failed task is a red "X".
- The NCrunch Tests window also has successful and failed "tasks", in this case the tests. However here there are two toggles, one for successful and one for failed tests.
3 votes -
Provide an engine mode to run only a specific project.
I have a solution that has many projects and each project has an associated test project. When I am working on project A, I only want NCrunch to run ATests, rather than ATests, BTests, CTests, etc. Currently, I can set the engine mode to pinned and pin my tests, but I have to manually pin all of the tests (I can only pin by class at most).
Also, I can setup a custom engine mode, but I would rather not have to have an engine mode per project.
Ideally, I would like a right-click option on a project in the…
3 votes -
Add the ExclusivelyUses attribute to the NCrunchConfiguration settings as an alternative to using the attribute.
If you could control the ExclusivelyUses values for a test, project, or assembly from the NCrunch configuration settings as well as using the attribute, the projects and solutions would not need references to the NCrunch.Framework.dll. So, for teams where only some developers are using NCurnch, the settings are kept for that user.
3 votes -
Edit entries in 'Additional Files to Include'
Put an Edit button in the Additional Files to Include dialog which is opened from the NCrunch Configuration window.
Would allow you to edit the path of an existing entry in the list, just now I have to remove and then re-add which is a little frustrating.
3 votes -
Add support for custom delegates with MSpec
MSpec supports Custom delegates.
Currently NCrunch seems hardcoded to "It", it would be great to support also custom delegates annotated with the AssertDelegate-Attribute
3 votes -
Use consistent wording in settings
When you describe the Spinner colours you use inconsistent language:
For example,
Outer circle colour on build failure
AND
Text colour when the build has failedShould be:
Text colour on build failure3 votes -
Show indication that the build is failing
Right now when the build is failing the line indication is that the test is failing. Technically, it is true. For the developer however, a failing running test, and a non compiling tests require different responses.
The spinner shows when the build is failing, but is in a very inaccessible placement on the far bottom right. This is not a place that we're used to looking at.
It would be much better, in my opinion, to have the line-dot color change to indicate build failure in addition to the spinner.
3 votes -
Force tests to run inside the same process
NCrunch spins up multiple processes to run tests. This is great most of the time.
But if a suite of tests has some expensive setup that only needs to happen once, that setup will run once for each process. Increasing the overall time it takes to run the whole test suite.
Provide a mechanism to force (suggest) NCrunch to run 2 tests in the same process. Something like a [SharedContext("Name")] attribute. Then when 2 or more tests are queued that have the same shared context, NCrunch should run those in the same process.
3 votes -
make grid nodes discoverable on the network
I think it would be great to use zeroconf or some such to provide a way to find available grid nodes on the network. Having to know the name or ip of each machine is cumbersome.
Would suggest requiring the user to assign trust to the nodes before they get used for any calculations though.
3 votes
- Don't see your idea?