Creating code coverage reports with NCover
Sergio Pereira just published a great article on creating code coverage reports with NCover and MSBuild over on devlicious.com. Check it out!
Update From NCover Central Command (or someplace close)
It has been way to long (besides yesterday) since we shared some NCover perspective about where we are headed with the next few versions that we have rattling around in our heads.
Sure, it's going to be cool. Maybe that whole "better than sliced bread thing". But the reality is that it will only get that way with your input and suggestions.
We want feedback...
So light up the conversation pipeline.
Tell us how you are using the platform. We want to know.
- Are you storing your NCover configuration in source control and having your developers pull down these setting?
- Do you have a workflow in place to merge together all testing activity across developer and testing roles?
- Are you using our control filters to divide large amounts of metrics into sizable reporting clusters that can be delivered to different management roles?
- What is your "coolest" NCover innovation yet? Your secret formula for deploying NCover?
Also, tell us what you want in our next versions? We want your feature included.
- Do you want a plug-in to Visual Studio? (Are you planning to upgrade to VS2010?)
- Do you better, faster access to all the data that we are collecting?
- Do you need to deploy and manage enterprise solutions more effectively?
We listen. You don't have to shout (although that could be fun). Just tell us about your dream product.
Quick Tip: NCover Explorer's Command Line
We've had a few users ask about opening coverage files with NCover Explorer from the command line. It's actually as easy as running it with the coverage file as a command line parameter. We also support opening project files on the command line.
So, the next time you're in the command prompt and want to open a coverage file, just run:
> NCover.Explorer Coverage.xml
