Feature Requests
297 results found
-
Reorganize settings based on events, not entities
E.g.,
On build Failure:
Outer Circle Colour – Dark Brown
Text Colour – Green
Line Marker Colour – Brown
Background music – Ride of the ValkyriesOn Test Failure
Outer Circle Colour – Red
Text Colour – Black
Line Marker Colour – Red
Background music – God Defend Visual Studio
….The reason is that humans are conditioned to think in terms of events. When “this” happens, I want “That”.
I.e., instead of thinking of
an entity, and all the events that can affect it,
we human like to consider
an event, and all the entities that are affected by…2 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 -
Clean up the noise when an AssertFailedException (or similar) is thrown
When an assertion in a test fails, you get the full stack trace of the AssertFailedException, which is noisy. For instance:
Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.HandleFail(String assertionName, String message, Object[] parameters)
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual, String message, Object[] parameters)
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual)
at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:[some likely really long path]\RectangleTests.cs:line 22Of all the above information, the only pertinent information is the message text of the exception and the bottom of the stack where the assertion failure happened. For instance:
Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:\users\floyd.may\documents\visual studio 2012\Projects\TestInheritance\TestInheritance.Tests\RectangleTests.cs:line 22Ideally, for MSTest, NUnit,…
14 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 -
Visual marker in far left margin when code is collapsed to definition
For those developers who do code maintenance by collapsing code to definitions (use Outlining Collapse) we can't see which tests in the file are failing at a glance. To see that we have to expand all the code to see the red/green markers.
All that would be needed is to promote a red or green top level marker to the far left margin to show us what test is failing in the file (when test method is collapsed).7 votes -
Show number of lines uniquely covered by a test
Today, the test fail/pass indicators on each line show which tests are executing that line.
I would like to have an option (maybe in the Metrics window) which tells me the number of lines covered solely by one test.
My goal behind is to identify code that is only run by few system/integration tests and clearly needs more tests. Such tests might start/run half of the system just to prepare a test so that - from the coverage point of view - the code looks like to be covered but - from the testing point of view - actually isn't…
4 votes -
Ignore Categories of tests
Note that this isn't the same thing as the enging mode not having a Category automatically run, etc. See http://forum.ncrunch.net/yaf_postsm6015_Ignore-categories-of-tests.aspx for more info.
24 votes -
Show risk information in code margin.
Show colour indicator and number indicator. Number will show how many tests cover that method and colour will say if its enough tests to fill safe.
2 votes -
Risk/Progress window move to toolbar (status bar) with progress bar. Add text "xxx/yyy test pass"
Risk/Progress window move to toolbar (status bar) with progress bar. Add text "xxx/yyy test pass"
Reason: unable dock this windows in right position when clip/unclip (auto hide ) dock panels.
1 vote -
Support Xamarin
Build an addin for Xamarin studio
34 votes -
Create an option to enable NCrunch only when on A/C power
I almost always develop on a laptop - but sometimes while travelling, and sometimes plugged in. I'd like NCrunch to automatically disable itself when I'm on battery power - it does suck energy like crazy - and then re-enable itself when I'm back on the grid.
12 votes -
Exclude from Metrics Aggregation by wildcard
Allow user to exclude files from Metrics Aggregation by wildcard. As an example, I'd like to exclude all *Designer.cs files from being counted.
17 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 -
Provide an option to only enable grid node when machines has no active user sessions
I'd love to make use of the latent power of all the locked desktops in my office but don't want to risk using nodes when someone is logged in.
1 vote -
Ncrunch Metrics Filter
The inclusion of a filter in the Metrics folder would be great. At the moment I have to export to excel and filter which doe snot give me a lot of options. Filtering by name and project and ability to exclude would be great
4 votes -
Option to disable stylecop MSBuild integration
Currently, FxCop Analysis can be switched off for Performance reasons. For the same reason it would be great to have a Setting where the StyleCop build Integration (http://www.nuget.org/packages/StyleCop.MSBuild/) can be switched off as well.
An additional benefit would be that there is no need anymore to occasionally reset the NCrunch test pipeline because of build failures (it cannot copy the StyleCop NuGet package which is at that time in use by another NCrunch process).
3 votes -
1 vote
-
Remote server: Run test on all (connected) servers
I have a test which is required to be run manually to reset the environment to a initial state.
I would like the option to run the test on all servers at once. Now I have to select "run test on server X" for each server I have which is tedious.(This feature would also be good to ensure a particular test is passing on all servers).
1 vote -
Support UITestMethod in Windows Store apps
Posted in response to: forum.ncrunch.net/yafpostsm5807UITestMethod-not-recognized.aspx.
Currently NCrunch ignores test methods with UITestMethod attribute which forces the test to run on the UI thread. This is required whenever the test needs to manipulate a UI element even if it's not a UI test in itself.
1 vote
- Don't see your idea?