NCrunch 3.11.0.9 Visual Studio 2008-2017 » Developer.Team

NCrunch 3.11.0.9 Visual Studio 2008-2017

NCrunch 3.11.0.9 Visual Studio 2008-2017
NCrunch 3.11.0.9 Visual Studio 2008-2017 | 5 Mb


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.

Changes in v3.11
*****
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.
*****

Fixed System.Threading.Thread package resolution issues causing IPC exceptions under .NET Core 2.0.

Fixed missing build binding redirection for XamlBuildTask assembly that was causing build-time issues
with some project types under VS2017.

Fixed several type conversion issues for MSTest DataRow tests that declare row parameters that differ
from method signatures.

Improved the handling of MSTest DataRow tests that pass enum objects into 'object' test parameters
when using MSTest under dynamic analysis. It is presently not practical to solve these problems
under static analysis (which is currently the default mode of operation for MSTest).

Fixed an issue where the engine was feeding previously removed tests into the pipeline, causing
downstream instability, especially with NUnit3 integration.

Fixed UI config setting for Workspace Base Path not working.

Removed the warning about AutoFixture incompatibility, as most use cases involving this toolset seem
to now be working correctly and this warning was unnecessarily scaring people.

Fixed an issue where NCrunch would fail to run .NET Core tests on systems without a
Microsoft.NETCore.App package installed in the current user's Nuget package cache.

Implemented handling for .NET Core 2.0's new package resolution fallback system. This should resolve
a range of package resolution and task environment initialisation errors present in some environments.

Fixed an issue where redirected reference assemblies were not being loaded by NCrunch from their
redirected location.

Fixed a potential IDE crash issue while painting NCrunch controls.

Removed code checking for whether the correct version of .NET Core is installed when preparing a test
environment, since this code doesn't seem to match with the range of undocumented rules used by
dotnet.exe in finding the .NET Core runtime assemblies and it was only causing things to unnecessarily
fail.

Adjusted the NCrunch.AllAssemblyLocations environment variable so that this variable can instead hold
the name of a text file that contains its contents. This is used as a fallback system for situations
where the size of the referenced assembly list cannot fit inside the environment variable block.
Under .NET Core and .NET Standard, the number of identified referenced assemblies has increased by
a significant amount. The NCrunch.Framework library has been updated to automatically load referenced
assemblies from the text file where this is used instead of the environment variable.

Fixed an issue where .NET Framework projects referencing a netstandard project under .NET Core 2.0
were failing to correctly load the netstandard.dll assembly at runtime.

Fixed an issue that was preventing NCrunch from correctly synchronising with grid nodes where Nuget
packages were being referenced that did not exist in the user's local Nuget cache (including primary
framework Nuget references).

Fixed an issue that was preventing NCrunch from being able to instrument assemblies under .NET
Standard 2.0 RTM.

Introduced a speculative fix to try and resolve intermittent server-side disconnection issues on
some grids.

Fixed an issue that was causing grid node servers to intermittently throw NullReferenceExceptions
shortly after synchronising with connected clients on some solutions.

Adjusted NCrunch's handling of unsupported projects to prevent malformed configuration files from
being created.

Fixed an issue where the current directory was not being set correctly in analysis tasks.




Only for V.I.P
Warning! You are not allowed to view this text.