Feature Requests
298 results found
-
Goto TestCaseSourceAttribute's source from Tests window.
I would be nice if it was possible to opt-in to change behavior of the context menu "Go to selected test" in that way:
With NUnit, one can write:
public static IEnumerable<TestCaseData> MyTestCaseSourceMethodName()
{
// return test cases...
}[TestCaseSource("MyTestCaseSourceMethodName")]
public void MyTest(int someArgument)
{
// do test...
}The test case factory method can be an separate (static) class.
In my case, I have a test with several dozens of test cases.When a test fails, I can easily go to the failing test implementation, but I cannot easily find the culprit test case.
2 votes -
Select current file in Metrics window
I would like to select the file I have opened in visual studio, in the metrics window, so I don't manually have to find it by clicking through the project structure.
Background: I have a build failing if metrics is below a threshold for specific files. When this build fails I get a list of file names. Then it is tedious for me to fix this "file by file" since I have no quick way of selecting current file in metrics window to verify my fixes.
2 votes -
Add predefined keyboard shortucts to switch between engine modes or make it possible to configure them manually.
As per title. Now doing it with mouse it way too inconvenient.
2 votes -
Attribute to identify type/methods that must have 100% code coverage
It would be helpful to have NCrunch treat (or at least report) decreases in code coverage as "fail".
For example, supporting an attribute that marks a project/class/method as "100% code coverage required".
Or a larger flag such that any code coverage drop is a "failure". This would be a bit trickier to support as it may need to be include a way to identify a baseline. And it may be helpful to distinguish between coverage for old code vs coverage for new code.
I think starting with a numeric attribute indicating the required coverage would give the biggest ROI --…
2 votes -
Test results formatting
Currently the test results appear as a block of text within the "NCrunch Tests" window. When compared to the built in display of test results in TestExplorer (im using VS2017), it feels rather raw and perhaps could be improved.
Im not saying to get rid of the raw text output (we all have our preferences), but to have an option to format the display of results to allow the result of a test to be clear and distinct from the full result text. So, instead of:
Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<2>. Actual:<1>. Some random failure description i typed in as the…
2 votes -
Add AlwaysImpactedAttribute for Run Impacted Tests Automatically mode
It would be useful if there was an AlwaysImpactedAttribute that could be attached to a test method so that it always executes when a code change is made.
The use case I am thinking of occurs with Automapper. We have a test that executes AssertConfigurationIsValid(), but when the engine mode is in "Run Impacted Tests Automatically" NCrunch will not detect that this test needs to be run whenever we make changes to the models in the solution.
If I could put an attribute on that test method that says 'always run', I could continue to use the "impacted only" engine…
2 votes -
Use project loaded in VS
Hi.
I want to be able to mark that nCrunch only use/load the projects that are loaded in VS.
Since our solution are becoming big, I use Funnel to load only the projects I need for my current task. But nCrunch still load all projects in my solution file.2 votes -
Let me resize the "Customise Engine Modes" window. ;)
it all in the title :)
2 votes -
Support [TestProperty]
MSTest allows us to tag tests with [TestProperty] attributes and their values are then available as this.TestContext.Properties.
However, ncrunch is not populating this dictionary, so a test using these attributes works in mstest/resharper, but fails in ncrunch.2 votes -
Enable "hotspots" indicators also for awaited asynchronous method calls.
I would like NCrunch to display the actual time taken for an async method to have been called, when using await, instead of showing 0ms, just like they do for ordinary synchronous calls.
See http://screencast.com/t/1mwMqiK0biExample code:
[TestFixture]
internal class TestFixture
{
private async Task FooAsync()
{
await Task.Delay(1000);
}
[Test]
public async Task AsyncTest()
{
await FooAsync(); //Coverage marker indicates 0ms duration.
}
[Test]
public void NonAsyncTest()
{
FooAsync().Wait(); //Coverage marker indicates 1s duration.
}}2 votes -
Provide parallelized execution time on Performance markers
Today, NCrunch shows the execution time across all threads on its performance markers.
If code is run in parallel, e.g.
Parallel.For(0, 100000, DoSomething);
the execution time is somehow misleading as it is not the real execution time (eg. 5 seconds) but instead the overall time (eg. 1 minute).
It would be nice if NCrunch would show both times, the actual time needed for the loop as well as the overall time accross all threads.
2 votes -
Be able to specify which class(es) a test is covering
I've noticed that in our test suite, various classes are showing as having code coverage through implict usage i.e. I'm testing class A, which is using class B within a tested method, and so lines of class B show as covered, when there's no dedicated tests for class B.
Technically class B is getting tested there, but it would be nice if we had an attribute we could optionally use (multiple times per class/method), which specifies which class(es) the class/method is testing.
[Tests<A>]
Then the code analysis will only calculate the LoC coverage for classes specified by the attribute(s) on…
2 votes -
Add short exception message column in Tests window
If there are multiple tests failing, you need to click each one and expand the bottom part of the window to read the text dump. It would save a lot of time if I could see the exception message beside each test. Especially for Asserts where I just want to see the expected value vs the actual value.
Ideally the message is formatted as "{Message} [{ExceptionType}]". AggregateException etc should be unwrapped when creating the short message.
2 votes -
Show coverage on LOC even when tests are excluded
We have a lot of integration tests that interact with the database, and as such, we flag these to be excluded from NCrunch using an attribute/customized engine mode.
While that is great, I would still like to be notified that the actual LOC are covered by something. Right now, I get the white dot/"no coverage"
It would be nice to still mark these lines as covered by a test - even if its excluded. Mark it with some other color, and let me drill into the tests in the test suite.
2 votes -
Allow projects to marked as no parallel execution
We have an integration test that has a setup task that get runs once before the tests execute to create and teardown the integration test database.
The problem with the way NCrunch executes is we get multiple instances of the database continually created (they have GUIDs in the name so they don't clash) but ideally I'd just like to be able to mark the integration test project to run all the tests in a single thread so the NUnit SetupFixture doesn't get run multiple times ... or if the are going to run in multiple threads to stop the reentrance…
2 votes -
Separate test output to separate dockable window
I sometimes work from home with 1 monitor and at work with 3 monitors. I also tend to like having test output in a less "important" place than the tests themselves.
With vstudio2015 the split setting (bottom or right) is not restored via the windows layout feature.
if test output was a separate window I can choose to place/dock it wherever I like (and also restore/save its position).2 votes -
Assign license key to developer name in mylicenses page
I'd like to be able to assign a company seat license to a developer's name. Currently under the https://www.ncrunch.net/User/MyLicenses page I can't figure out which key is being used by which developer.
As my team grows and as developers come and go this becomes a more time consuming process to manage. I'd rather not do this via another spreasheet.
2 votes -
inherit colors from environment
I don't use Windows default colour scheme. Instead, I reduce the amount of light hitting my eyes by using a black background and green text (very retro, ha ha). Some NCrunch windows / dialogs set their background color to grey, which makes green text difficult to read.
So, please, don't override my local settings, just allow your windows / dialogs to use whatever colours I have already set up for myself.
Thanks!
2 votes -
Be able to Bind a key (F5) to run debugger in the current test cursor located in
It would great to use the muscle memory of pressing F5 to debug code, by allowing the functionality of "Right click on a unit test and select Debug starting test in new task runner process" to happen based on where the cursor is currently located.
2 votes -
Add 'Clear search' button next to "Text to search on" in "NCrunch Tests" window
It'd be useful to clean the search text in one click, similar to OOTB VS and other software experience.
Right now we have to focus on the text within the search box, then double click and delete, or backspace a lot.
Out of the box VS test window has that little button to clear the search, as well as other systems do.
Matter of habit and efficiency while working with UI across various apps.
2 votes
- Don't see your idea?