Feature Requests
288 results found
-
Attribute to enable tests with "shared resource" to run on same server within same "session".
Original thread: http://forum.ncrunch.net/yaf_postst1368_Restrict-multiple-tests-to-run-within-same-grid-node-in-console-runner.aspx
This is primarily for the console test runner (or e.g engine mode "run all tests within automatically").
Scenario: I have some integration tests using large test data. This test data is created once and then reused between these tests. When using grid nodes tests using same "test data resource" might end up running in different grid nodes, causing each test creating new test data (which makes the tests slower than if they were run in serial).
It would be nice to have an attribute e.g. [SharedResource("TestBlob")] making all tests with same "shared resource" to be run within…
1 vote -
Allow specflow scenario outline examples to have their own 'dot marker' in the margin
currently if you have a scenario outline that has several examples there is no way to run a specific example as a test, I can only see the dots in the actual scenario outline and have to then run 'x' number of tests at once (where 'x' is the number of scenario examples)
I'd like a 'dot' by each line in the examples so I could run a specific scenario example on its own or see which example is actually failing
9 votes -
Show the PID of process in which a test is running
I whish to be able to see the PID of the currently running test when I break in it. Thus to allow to attach a performance analyzer.
1 vote -
Using XBox as NCrunch Grid node server
When i'm programming my xbox is idle. it would be awesome if I could run ncrunch builds and test on it.
10 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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
1 vote
-
Test pass/fail in Enhanced scroll bar or R# scroll margin.
The ability to have NCrunch show the code coverage and test pass/fail in the enhanced scroll bar from power productivity tools or Resharpers scroll bar. Or something similar. That way can tell if tests that are not visible on screen change. Of course could have the tests window up...
7 votes -
Allow coverage marker colour to be defined for tests in progress
When tests execute the colour of the coverage markers darken. This is very useful for determining when affected tests have completed. However, the contrast is too subtle. It would be good if this could be changed in the 'Coverage Markers' configuration section. Either with an absolute colour or at least to have control over the percentage of darkening.
2 votes -
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?