Feature Requests

  1. Add support for custom delegates with MSpec

    MSpec supports Custom delegates.

    https://github.com/machine/machine.specifications/blob/master/Source/Examples/Example.CustomDelegates/Delegates.cs

    Currently NCrunch seems hardcoded to "It", it would be great to support also custom delegates annotated with the AssertDelegate-Attribute

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow to temporarily ignore tests

    When some tests are failing for a known reason (eg: When making structural changes, or when developing to an interface which is not yet completed), it would be nice if there is a possibility to tell the NCrunch Tests window to ignore certain tests for a defined period of time.

    For example:
    right-click test in the list

       > Ignore.. 
    
    > Ignore for 10min
    > Ignore for 1hr
    ....
    > Ignore for today

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. When showing coverage for specific tests show icon against them in 'NCrunch Tests' view

    When I show coverage for a specific test I trace through the code paths which are being executed using the per line coverage, however sometimes I then need to debug through that test, it would be nice if I could easily see which test is currently showing coverage so I can debug it

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Option to always start NCrunch disabled

    I frequently switch between working copies/branches and since I use an engine mode which is automatically running tests I would to manually enable NCrunch on startup. This since the test suite is very heavy and I might want to open solution without immediately running all tests and/or I need some changes to e.g. "Custom environment variables" so tests are running correctly.

    (Now I need to remember to disable NCrunch before closing project, which I most often do not remember. Also the now and then occasional vstudio crashes prevents me from setting this)

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Doubleclicking a failing test should jump to the failing line

    If I doubleclick a test in the tests window the test, the file containing the test is opened in the IDE and the cursor jumps to the beginning of the test (Feature: Go to selected test").

    It would be nice to have a "Go to selected test at failing line" feature that can be accessed via right click a failing test and even being able to set this as default action for double click.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Display test output in text window (on button click)

    We use extensive logging information to analyze test failures.

    Currently the test output is only displayed in a split window of the tests window. This makes reading and analyzing long test outputs (especially with long lines) rather difficult.

    Therefore it would be nice to be able to display the test output with one button click in a separate (temporary) text window (similar to the Visual Studio test runner).

    Posted in response to: http://forum.ncrunch.net/yafpostsm5490Ability-to-display-test-output-in-text-window.aspx#post5490

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add a way (toolbar button ideally) to pin visible tests.

    Often I want to pin failing tests, then make a change so a large number pass, then I want to unpin the passing ones. I can unpin all, show only failing then would like to pin all visible.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Attribute to exclude specific tests from automatically running

    I have several unit tests and integration tests within the same project. It would be great to have an attribute to exclude the integration tests from automatic runs. These tests would only be trigger-able manually

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Detect Microsoft.Net.Compilers references and automatically copy it to the workspace

    The Microsoft.Net.Compilers package allows projects to use a specific version of the compiler. When NCrunch attempts to build a project referencing that package it will fail by default with the error: "packages\Microsoft.Net.Compilers.2.4.0\build..\tools\csc.exe" is invalid." The current workaround is to add the tools directory for that package in the "Additional Files to Include" dialog.

    NCrunch should recognize that this package is unique and handle it automatically.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add window showing slowest lines of code

    The slow hotspot markers were super useful in me rewriting portions of test / application code to speed them up.

    It would be useful to be able to see a list of the slowest lines of code so attention can be given to refactoring them.

    Bonus points if this can be sorted based on total time under test, and also average time under test

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. allow copy paste from exception details window

    It would be helpful to be able to be able to copy paste text from the exception details popup that displays when you click the X mark in the ncrunch gutter, e. g. stack trace, exception message, ...
    Right now, the test has to actually be executed in debug mode in the task runner to be able to copy text from the standard visual studio exception popup window

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow to rerun all tests matching current engine mode

    If I have 2 engine modes "Manual" and "All Automatically except HttpTest", I must toggle between the 2 in order to re-execute all tests.

    I would want a way to execute all tests matching the active engine mode, without having to toggle between "Manual" and the one I would want to be re-executed.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow negative wildcard inclusions

    NCrunch allows you to add files and directory to include in the workspace using file globbing patterns. This is a great feature. However, this feature could be improved to also allow you to specify "negative inclusions", which would greatly benefit large solutions.

    My solution has 107 projects in it and one of the projects is a test project that runs some "solution-wide" tests using Roslyn Compiler Services. So this test project requires that the entire solution be in the workspace. However, what I don't need are all the {bin,obj}*. files, just the .cs and .csproj files.

    Currently, it's really difficult…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Engine mode condition to allow distribute processing only of some tests

    Summary: I would like to specify an engine mode e.g. "Run db tests locally, all other distributed".
    Details: I would like to define grid nodes condition in the NCrunch engine mode settings. A first simple step would be to add setting similar to "Tests to execute on this machine", but under the Distributed Processing node. This way I can ensure no test with category [DbTest] is executed on grid nodes, but only on local (where I have the test db set up).

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Include Process Id in NCrunch Console Timeline report

    I would like to see when NCrunch starts up a new, or reuses existing, process in the NCrunch Console Timeline report, so I can find if long test run duration is due to process startup time or due to slow test run.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Run same test with different configuration options (similar to NUnit's TestCase)

    Let's say I need to support 2 db providers (e.g. SqlServer and Sqlite) and I write the same (1) test for both but in the configuration file for the test project I define which db provider it should connect to.

    Currently the work process is something like:
    1) Run all tests with SqlServer provider setting set
    2) Change configuration file to use Sqlite provider.
    3) Re-run all tests to tests towards Sqlite provider.

    What I would like to have is something like:
    1) In a setting for a test project, define x number of "environment configurations" where I guess the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Option to hide NCrunch warnings per user

    I would like a solution setting so clicking "Click here to hide this warning" ends up in my .ncrunchproject.user instead of team shared .ncrunchproject file.

    Background:
    I have a lot of warnings in projects I am hiding, after validating they are valid to ignore. If I am not experienced with NCrunch I probably do not know what they mean, hide it and commit changes to .ncrunchproject files.
    The warnings also include grid nodes warnings, which might only be specific for my machine (if we e.g. do not share grid nodes for the team settings) and really makes no sense to…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. improve indicators for explicit and ignored tests

    I use Nunit but I guess there are similar concepts for other test frameworks. Currently any explicit or ignored tests have white icons in the editor and show as unexecuted in the tests window.

    I would like the option to change these indicators. In particular to change the colour/shape for the ignored/explicit tests icon in the editor.

    I would also like a filter for both explicit and ignored tests in the tests window. This would help me to track these tests down quickly

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow AssemblyVersion to be ignored in order to prevent errors in NCrunch

    If the AssemblyVersion attribute contains an asterisk (eg "1.0.0.*") then NCrunch cannot reliably build the solution.

    Currently, there is no way to prevent NCrunch from resolving the AssemblyVersion of each project and this causes problems with inconsistencies and NCrunch reporting build errors because MSBuild is expecting a different version of the assembly to the one provided.

    The current alternative to this involves polluting non-test project files with NCrunch-related hacks, which is not very clean.

    In order to resolve this issue, I suggest that a setting feature be added to NCrunch which allows AssemblyVersion resolution to be disabled.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base