NCrunch 2.24.0.2 Visual Studio 2008-2015
NCrunch 2.24.0.2 Visual Studio 2008-2015 | 18 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 v2.24
*****
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.
*****
New Features:
Added a new return result to the console tool (exitcode 5), indicating when no errors or failures were
encountered but some tests were not executed during the run.
Added the number of connected grid nodes to the corner spinner tooltip.
Fixes and Compatibility Improvements:
Fixed a compatibility issue with NUnit 3.4.1, where errors encountered during test discovery would cause tests
to be lost from NCrunch's model.
Fixed a performance issue that could cause the VBCSCompiler.exe process from stealing CPU away from VS when
working with NCrunch.
Fixed a serious issue where deleting the entire contents of a tracked source file would result in permanent
corruption of NCrunch's code coverage data. The only way to solve this was deletion of NCrunch's .cache file.
Fixed an issue where tests were not correctly being marked as outdated when the engine was initialised. This
had the potential to create misleading results during execution runs of the NCrunch console tool.
Fixed an issue where the engine would hang during initialisation if a project experienced a load failure and
the 'Infer project references using assembly names' setting was enabled.
Strengthened the error handling around the loading of cached data. This should help to prevent the engine
entering a critically failed state in the event of cache data corruption.
Added additional information to the 'NUnit tests have been detected with the same name' warning to help people
better understand why this issue exists and how to solve it.
Fixed several potential crash/performance issues when working on systems with 32 processors or above.
Fixed issues with the 'Configure selected components' option not working correctly when the configuration
window was closed.
Fixed an issue where blank coverage markers could be shown in some circumstances where there was no actual code.
Fixed an issue where resizing the tests window output pane could result in the scrollbar being removed and the
output text locked above the view pane.
Fixed inconclusive MSTest tests being reported as failing when using ExpectedException and the
'Consider inconclusive tests as passing' setting is enabled.
Introduced a fallback routine for when coverage mapping problems are encountered. This should allow the engine
to continue relatively normally if something goes wrong.
Added codes to build warnings for NCrunch builds.
Fixed an issue where commenting out a line of code being executed by a background test run could cause code
coverage corruption.
Fixed an issue where content/resource files with a 'link' property set were not being copied to the correct
build output directory when the 'Copy referenced assemblies to workspace' setting was enabled and project
references were 2 levels deep or above.
*****
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.
*****
New Features:
Added a new return result to the console tool (exitcode 5), indicating when no errors or failures were
encountered but some tests were not executed during the run.
Added the number of connected grid nodes to the corner spinner tooltip.
Fixes and Compatibility Improvements:
Fixed a compatibility issue with NUnit 3.4.1, where errors encountered during test discovery would cause tests
to be lost from NCrunch's model.
Fixed a performance issue that could cause the VBCSCompiler.exe process from stealing CPU away from VS when
working with NCrunch.
Fixed a serious issue where deleting the entire contents of a tracked source file would result in permanent
corruption of NCrunch's code coverage data. The only way to solve this was deletion of NCrunch's .cache file.
Fixed an issue where tests were not correctly being marked as outdated when the engine was initialised. This
had the potential to create misleading results during execution runs of the NCrunch console tool.
Fixed an issue where the engine would hang during initialisation if a project experienced a load failure and
the 'Infer project references using assembly names' setting was enabled.
Strengthened the error handling around the loading of cached data. This should help to prevent the engine
entering a critically failed state in the event of cache data corruption.
Added additional information to the 'NUnit tests have been detected with the same name' warning to help people
better understand why this issue exists and how to solve it.
Fixed several potential crash/performance issues when working on systems with 32 processors or above.
Fixed issues with the 'Configure selected components' option not working correctly when the configuration
window was closed.
Fixed an issue where blank coverage markers could be shown in some circumstances where there was no actual code.
Fixed an issue where resizing the tests window output pane could result in the scrollbar being removed and the
output text locked above the view pane.
Fixed inconclusive MSTest tests being reported as failing when using ExpectedException and the
'Consider inconclusive tests as passing' setting is enabled.
Introduced a fallback routine for when coverage mapping problems are encountered. This should allow the engine
to continue relatively normally if something goes wrong.
Added codes to build warnings for NCrunch builds.
Fixed an issue where commenting out a line of code being executed by a background test run could cause code
coverage corruption.
Fixed an issue where content/resource files with a 'link' property set were not being copied to the correct
build output directory when the 'Copy referenced assemblies to workspace' setting was enabled and project
references were 2 levels deep or above.
[/b]
[b]
Only for V.I.P Warning! You are not allowed to view this text.