NCrunch 2.14.0.8 MSVS 2008 - 2015 CTP » Developer.Team

NCrunch 2.14.0.8 MSVS 2008 - 2015 CTP

NCrunch 2.14.0.8 MSVS 2008 - 2015 CTP
NCrunch 2.14.0.8 MSVS 2008 - 2015 CTP | 22 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.14

Introduced code navigation ("Go-to") options. This allows easy navigation via shortcut key to tests,
build failures and test exceptions. All shortcuts can be found in the "Go to" NCrunch VS submenu.

Updated XUnit V2 integration to the RTM.

Fixed several issues in XUnit V2 integration that were preventing some extensions from working correctly.

Fixed an XUnit V2 integration problem that could cause theory results to be misreported.

Adjusted the rendering code of the Distributed Processing Window to improve performance.

Fixed an issue where exceptions thrown on background threads during testing were not causing tests to fail
for XUnit and MSpec tests.

Fixed an issue where the grouping structure of the Tests Window was not being correctly saved between sessions.

Added a new test count summary which is shown in brackets next to parent nodes inside the Tests Window.

Introduced a new toolbar option to the Metrics Window that allows you to tell NCrunch to ignore test
projects when calculating metrics.

Introduced a new state image for projects in the Metrics Window that can differentiate test projects from
non-test projects.

Fixed an issue that was preventing NCrunch from correctly pipelining tests which have experienced changes
in their RequiredCapabilities or Test Filter pass/fail result.

Adjusted the handling of debugger test tasks so that these are now exempt from the local client Test Filter.
This is because Test Filters make no sense in this situation, as debug tasks can only be run on the local
machine and will simply hang in the queue if they are excluded using a Test Filter.




[/b]

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