I couldn’t help but take a quick search through Twitter
for what you are saying about NCover — especially after the rapid fire release of 3.1 a few days ago.
Certainly GraemeF seems to believe that we are indeed developing NCover.
Let me put this rumor to rest. We are developing code quality solutions like mad men and <secret> we are planning sweet integration with the latest Visual Studio 2010 WPF IDE “goodness” Microsoft is delivering. Expect big things. Suggest big things…
Certainly Shane is jazzed about TestDriven.net and NCover working together to produce method-level quality analysis.
We agree that TD.net is a “must buy” and so is NCover. Take two or three with you to share with your buddies.
Certainly Ruby_Gem loves how NCover magically creates unit tests for her. Did I hear something about a special exercise program?
Absolutely, Ruby, we will be doing the code pilates right beside you. You must have had a look at our secret plans for world domination. It is amazing how the idea of testing becomes a lot easier with the right tools.
Certainly Kkozmic has an opinion on how NCover compares to the rest of the code quality tools on the planet (perhaps even the universe).
Well, I happen to agree with out friend Kkozmic. We do claim to “fly like a butterfly, sting like a bee”. And in all seriousness, we do work hard to keep pushing out features and a quality product.
Last, but certainly never least important, I leave you with our Confucius thought of the day from PaulLiebrand.
Certainly PaulLiebrand asks the right question: “Do you love NCover? Anybody using this thing? Tell me your experience…”
I re-blog-tweet his thought and counter with an invitation to hear our CEO talk code quality with the zen-masters from Innerworkings. Bring your twriends with you…
Throw out the models that show how expensive it is to let bugs make it into product deployment. Bugs are expensive, but they just might cost you even more in the coming months. Recent frustration with software quality has led the European Commission, to consider making software creators liable (i.e. getting sued) for writing bad code.
That’s right…. The cost of bugs just went up. CNet broke the story about a week ago and since then the blogosphere has exploded with comments, frustrations, and insight into the possibility that software companies might have to suffer more than just an angry customer or a public flaming:
“A priority area for possible EU action is ‘extending the principles of consumer protection rules to cover licensing agreements of products like software downloaded for virus protection, games, or other licensed content,’ according to the commissioners’ agenda. ‘Licensing should guarantee consumers the same basic rights as when they purchase a good: the right to get a product that works with fair commercial conditions.’
EU consumer commissioner Meglena Kuneva said that more accountability for software makers, and for companies providing digital services, would lead to greater consumer choice.”
Certainly any such advocacy has to expect to encounter massive international resistance. It would seem that applying Underwriter
Joe and Steve, our lead developers, and the entire NCover team are pleased to announce that we have released NCover v3.1 today. We listened to a ton of great feedback from the community about our v3.0 platform and went to work to make the leading .NET code coverage platform EVEN BETTER. Thanks for your help! A new key is not required if you are upgrading from NCover v3.0; just download, install and run.
You will already notice the new website that Ethan, Kevin and Alan spun up. We hope you like it as much as we do. Check it all out: better access to answers, better videos to get you started, and better navigation.
Take a moment to check out our partners, linked at the bottom of the page, while you download v3.1. Check back over the next few days as Joe will be working on explaining his new “diff” and trending reports that are part of this release. Until then, here is everything you wanted to know about the new product release:
Features and Improvements
- Added Trend Reporting
- Added Difference Report (The “Diff”)
- Added new //xslt flag which allows for loading of a custom xslt file for the reports.
- Added new //literal flag allowing you to ignore the corrections we make when covering child processes using MSBuild and Gallio.
- Acceptable Branch Percentage is now supported in the IDE and in all reports except FullCoverageReport.
- Acceptable Cyclomatic Complexity is now supported in the IDE and in all reports except FullCoverageReport.
- Added the ability to toggle if we should ignore failed builds in the Trend graph.
- Added the ability to sync the coverage file exclusions back to the project (on by default).
- Added the ability for the //cr to be specified multiple times from the ncover.reporting command line.
- Updated the text and visuals on the RebasedSourceWindow depending whether it is looking for a missing or an out of date file.
- You are now able to click on Project split button to load project options instead of using the “Manage Options” button.
- You are now able to click on Coverage split button to load coverage file options instead of using the “Manage Options” button.
- Module is now called assembly everywhere.
- Sequence Points are now called Symbols.
- Sample code now contains a link on the program menu.
- Arguments appearing after a config-read statement now override settings in the config file, instead of being ignored.
- Updated documentation to refer to //or instead of deprecated arguments.
- The //at flag on the NCover.Console command line would create an exception if the file didn’t exist.
- If //h was used, NCover.Console ignored it and output the report to the current directory instead.
- Bugs with the //sct flag.
- Fixed bug where sct view options were not being placed on the view. We now add the view level items to the view first and everything will inherit from it correctly.
- The FullCoverageReport now treats arguments from the //op and //or parameters as directories, like the documentation says it does and like 3.0.18 did.
- The FullCoverageReport now clears out the files\ sub-folder if it exists when a report is created.
- The algorithm that merged modules together as they came out of shared memory was merging instrumented points based solely on the offset, when it should have been merging based on offset and the type of point (symbol, branch, etc).
- The type name of the CyclomaticComplexity object was being displayed instead of the maximum value when an object failed a CC threshold.
- Fixed bug where we were showing “load trends” on the trend graph when a trend file was loaded in the graph.
- Update the graph if you change the report style
- Added missing MergeFilterMode for MSBuild and NAnt task items
- Fix bug where if the list was less than the max fail to show, the entire list would be displayed. We now correctly limit the list to the max you tell us to use.
- When the Rebase Source Window was launched from the search pane, it would throw an exception when it closed.
- If a missing source file was ‘ignored’ by the user, NCE wouldn’t load it, but the next time they clicked on the class NCE would ask them to locate the ‘ignored’ file.
- If multiple classes were in the same missing source file and the user ‘ignored’ the first request, NCE would ask the user to locate the missing source file once for each other class in the source file.
- Assemblies were not being filtered correctly due to the fact the name was fully qualified, including the version metadata. You no longer have to use a trailing * for the filters to work correctly.