NCrunch v4.1 for Visual Studio 2008-2019

NCrunch v4.1 for Visual Studio 2008-2019
NCrunch v4.1 for Visual Studio 2008-2019


It intelligently runs automated tests so that you don't have to, and gives you a huge amount of useful information about your tested code, such as code coverage and performance metrics, inline in your IDE while you type.

Automatic Concurrent Testing
A normal cycle of test driven development makes you stop to run your tests so often that it's just plain painful. Think about the steps you usually go through:

Write the test
Stop and run the test
Write the code under test
Stop and run tests
Refactor the code under test
Stop and run tests
Drink some coffee and repeat

NCrunch takes away all the pain and leaves a warm happy feeling behind. So you end up with:

Write the test
Write the code under test
Refactor the code under test
Be happy, drink some coffee and repeat!

Code Coverage
NCrunch collects test coverage for your code while it runs your tests.

This is shown next to your code in coloured markers showing which lines the tests touched, with marker colours indicating pass or fail status.

You can also navigate to any covering tests from any line of code, making it easy to see which tests you might impact with a change.

Full code coverage metrics are also available for your entire solution, allowing you to see where your code coverage is heavy and where it's light.

Performance Metrics
NCrunch profiles your tests during their execution to pick up the execution time of every line of code under test.

Metrics are shown inline conveniently with a tooltip, and 'hot spots' are shown with special colouring on the code coverage markers.

Inline Exception Details
The stack traces of exceptions thrown from your tests are processed by NCrunch and projected over the code coverage markers.

This makes it really easy to spot where your tests went wrong, without the information getting in your way.

No matter where you are in your source code, you'll be able to analyse problems quickly and without fuss.

Intelligent Test Execution
NCrunch tracks all sorts of interesting statistics about your tests, and it uses this information in the most intelligent way possible.

Tests that you have recently impacted with your code changes are highly prioritised for execution.

NCrunch uses a powerful weighting system designed to give you the most important feedback as fast as possible.

Distributed Processing
NCrunch can offload build and test work to other computers for processing.

Tasks are cleanly farmed out to any number of connected machines, forming grids to execute tests.

Grid servers can be shared between developers allowing teams to pool their resources.

Grids can even be scaled into the cloud to maximise testing throughput.

Distributed processing with NCrunch is highly effective, allowing concurrent execution of dozens or possibly even hundreds of tests at any one time.

-----------------------------------------------------------------
Release notes for 4.1.0.1 since version v4.0.0.2
-----------------------------------------------------------------

Fixed an issue that would cause an exception when trying to process a generic class containing an async
method under optimised mode.

Hardened the resolution of async methods to better deal with unexpected structures under optimised mode.

Remove millisecond unit from time span columns when exporting to csv or text files.

-----------------------------------------------------------------
Release notes for 4.0.0.2 since version v3.31.0.3
-----------------------------------------------------------------

*****
This version of NCrunch introduces changes to the grid protocol. This means that grid node servers
must be updated before they can be used with the new version.
*****

BIG FEATURE RELEASE: Introduced a new IL-processing/instrumentation system giving a massive improvement
in performance, and a new feature area for analysing line execution times in bulk (global hot spots).
For more information on these major changes, please see https://blog.ncrunch.net/post/NCrunch-V4-Released.aspx

Restructured the handling of code coverage data to improve performance. This should significantly reduce the
runtime lag caused by the tracking of code coverage data when executing many small tests inside a single
execution task.

Added the option to filter on project names with regular expressions when using filters on an engine mode.

Added a button to the metrics window to reset the excluded metrics.

Fixed a problem with determining the correct target when a netcoreapp2.1 or 2.2 project was referencing a
multi targeted project that targeted netstandard2.0 and netstandard2.1

Made a performance improvement in the UI when the engine is reporting the status of lots of tests.

When running under .NET Core, tests will now use the server GC with concurrent garbage collection disabled.
We've recently observed some strange rare abnormalities related to concurrent garbage collection in the NCrunch
test environment and are hoping this change will resolve the problems and may also yield some performance benefit.

Fixed an exception being thrown when setting the data storage path in the Grid Node Configuration wizard.

Introduced a workaround to the project loading system so that .razor files are considered code files by
NCrunch, even though the build system reports them as content. This should allow NCrunch coverage markers
to show on these files.

Improved the error reporting when a build task fails unexpectedly.


Information
Users of Guests are not allowed to comment this publication.