pete

← NCrunch Feature Suggestions

My feedback

  1. Allow an ignored test to be run manually

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    pete shared this idea  · 

  2. Add predefined keyboard shortucts to switch between engine modes or make it possible to configure them manually.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    pete shared this idea  · 

  3. Show what it the currect engine mode on "NCrunch Test" screen or maybe via some icon in the VS status bar.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    pete shared this idea  · 

  4. Pause while nuget is installing or updating packages

    101 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    6 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →

  5. Integrate with the upcoming project rider, similar to what WallabyJS does

    211 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    25 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    pete commented  · 

    IMHO Damian Hickey described it perfectly.
    Also the suggestion to partner with JetBrains is a very interesting idea that you should seriously consider IMHO.
    Another option is to open up the "protocol" for other to implement the UI they want for tools they use. I'm sure that VSCode people would be very happy to do it and JetBrains IDEs have a lot of plugins as well.
    I'm aware this imposes some limitations on your work and future NCrunch development, but it might be a good choice regardless of those.
    From your forum response I'm guessing that you did couple NCrunch to VS too much and that's probably something you should fix ASAP in this changing landscape to continue to have success apart from keeping up with testing framework to make NCrunch work well in the meantime.
    At the moment NCrunch is the best tool of its kind so IMHO you should not feel the need to introduce a lot of new features and use this time to ensure that NCrunch is safe for the next couple of years.

    An error occurred while saving the comment
    pete commented  · 

    NCrunch is THE ONLY reason I stick to Visual Studio.
    I hate VS and will leave it as soon as NCrunch works with Rider or Rider does Continous Testing well.

    pete supported this idea  · 

  6. Standalone UI which can be used with every other IDE

    16 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    pete commented  · 

    I fully support this idea.
    IMHO that's the right way to move forward.
    It's the only good future for NCrunch.

  7. Allow the console tool to be run continuously

    16 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →

Feedback and Knowledge Base

(thinking…)