#10 NCover 4 has 3x the flexibility — Desktop, Code Central and Collector.
NCover 4 has been designed around where you use it, so you no longer have to force one standard code coverage tool into many usage scenarios. Desktop is built to make developers lives easier by providing code coverage metrics right on their personal machine and inside their Visual Studio interface. Code Central lives on the build server providing metrics on team wide code coverage and instant access to detailed reporting features. Collector affordably gathers coverage on machines remotely and sends the results back to Code Central.
#9 NCover 4 now runs as a service.
NCover is no longer a windows application… it is now a service that is continually running in the background. This allows NCover to immediately detect when you’ve started testing an application previously designated in a project. Therefore, once you’ve set a project up you can gather coverage without modifying your normal work-flow in anyway.
#8 NCover 4 displays execution identifying details for each coverage run.
Previously if you wanted to save details about a test execution like build id, date, time etc. you had to track it on your own. Now it’s all contained within automatically within our reporting interface and even allows you to customize the results with an edit feature.
#7 NCover 4 merges executions with the click of a button — un-merge just as easy!
Because NCover now runs as a service you view all your code within a browser window like Chrome, Firefox, Internet Explorer, etc. This allows for a far more dynamic interaction with your coverage results including the ability to merge results from multiple executions with a click of a button… and un-merging is just as easy (previously not even possible).
#6 NCover 4 now calculates your code’s CRAP score.
One of the most important metrics NCover provides is a CRAP (Change Risk Anti-Patterns) score which is a correlation between your codes complexity and your code coverage. This metric creates clarity about both your codes health as well as helps to prioritize your testing efforts. You can find details about all of NCover metrics here: http://www.ncover.com/support/docs/v4/getting_started/code-central/how-do-i-view-data/coverage-metrics.
#5 NCover 4 Code Central provides access to coverage data from anywhere.
You are no longer are reliant on reports being created and shared among the team; you can now login to Code Central from anywhere and access the most recent coverage data instantly. No more waiting.
#4 NCover 4 now integrates coverage results within Visual Studio.
With NCover 4 Desktop you can now configure, run, and view all your code coverage without ever leaving Visual Studio. Once you’ve gathered your coverage data you have a number of options for viewing your metrics… you can simply choose to view code highlighting or you can have up to three separate viewing panes showing detailed feedback on your tests. The plugin also includes NCover’s new branch visualization showing possible branch scenarios and highlights which branches have been covered and which haven’t.
#3 NCover 4 auto-configure for projects makes configuration a snap.
Setting up a project now takes just a few minutes with our new auto-detect feature. You simply start auto-detect, start your application, choose what you want NCover to profile and save the project. Adding additional options like inclusion/exclusion rules are still available but much easier to setup during the auto-detect process… if you want to exclude portions of your application simply uncheck them.
#2 NCover 4 shares coverage by syncing data to Code Central from Desktop & Collector.
Both Desktop and Collector can be connected to Code Central to sync your project’s coverage numbers in seconds. Setting up the sync takes less than a minute, you can sync as many machines as you need with Code Central, and once you have them configured syncing happens automatically with each test run.
#1 NCover 4 no longer requires long complicated command line syntax.
One of the most difficult parts of NCover 3 was the time consuming process of building and configuring your command line syntax on each project. With NCover 4 you never have to build another command line before gathering coverage… even if you choose not to use auto-detect you can still have a project configured and gathering coverage in a fraction of the time previously needed.