JetBrains to Launch dotCover EAP Next Week
March 24th, 2010 by Jura GorohovskyThe first half of 2010 turns out to be pretty fruitful for .NET developers who use JetBrains tools. In addition to upcoming major releases of ReSharper and dotTrace, we’re extending our .NET toolset with dotCover — a code coverage tool.
Many of our customers consider unit tests a vital part of their development workflow. It doesn’t come as a surprise that we want to let them easily see how successful they are in covering their applications with tests. To bring an extremely comfortable code coverage experience to developers, the initial version of dotCover will introduce the following features:
- Integration with Visual Studio 2005, 2008 and 2010.
- .NET projects coverage in Visual Studio.
- Test coverage through tight integration with unit test running engine in ReSharper 5.0.
- Navigation to source code from coverage report.
- Highlighting for covered and uncovered code in Visual Studio code editor.
- Navigation from source code to unit tests that cover it.
We’re thrilled to announce that some of these features will be available via Early Access Program that we’re launching next week. Stay tuned for an additional launch announcement here on the .NET Tools Blog and follow us on Twitter.
Tags: dotCover, eap, unit testing
March 24th, 2010 at 1:09 am
Great!
Any chance we could see a command line version of this beauty to add to the build server?
March 24th, 2010 at 1:24 am
[...] The rest is here: JetBrains .NET Tools Blog » Blog Archive » JetBrains to Launch … [...]
March 24th, 2010 at 3:06 am
That’s great news. I’d love to have a code coverage tool tightly integrated with ReSharper. Is there any chance that users of both products could get a discount on a developer bundle that included both products? And possibly dotTrace as well?
March 24th, 2010 at 3:09 am
Is is going to be possible to use dotCover via a command line build?
March 24th, 2010 at 3:11 am
AWESOME!
I was asking myself when you will do it. And I guess I already asked you the question too.
March 24th, 2010 at 4:39 am
Social comments and analytics for this post…
This post was mentioned on Twitter by gorohoroh: JetBrains to launch .NET code coverage tool next week : http://bit.ly/dotCover...
March 24th, 2010 at 4:59 am
That’s awesome
March 24th, 2010 at 10:50 am
[...] Read more 6882dbf0-6195-43ed-8891-b7580fb0e9f3|0|.0 [...]
March 24th, 2010 at 10:51 am
[...] JetBrains to Launch dotCover EAP Next Week - JetBrains announce their new product dotCover, a code coverage tool which integrates tightly with Visual Studio 2005, 2008, and 2010 and Resharper, providing feedback on test coverage. Initial Early access releases will be available from next week. [...]
March 24th, 2010 at 10:54 am
Hello
Will it be part of ReSharper or will it be a seperate tool that integrates with ReSharper?
Cheers
Gabriel
March 24th, 2010 at 11:44 am
Sounds great! Any idea of how this will be priced yet?
March 24th, 2010 at 11:54 am
Great news, I believe your product will be much more better and more bagfree than NCover :))
March 24th, 2010 at 12:24 pm
[...] JetBrains .NET Tools Blog » Blog Archive » JetBrains to Launch dotCover EAP Next Week blogs.jetbrains.com/dotnet/2010/03/jetbrains-to-launch-dotcover-eap-next-week – view page – cached The first half of 2010 turns out to be pretty fruitful for .NET developers who use JetBrains tools. In addition to upcoming major releases of ReSharper and dotTrace, we’re extending our .NET toolset with dotCover — a code coverage tool. See all Top 5K for jetbrains.com Filter tweets [...]
March 24th, 2010 at 1:17 pm
@Sean
Pricing info will be available a bit later, sometime around dotCover Beta release I think
@Gabriel
It’s a separate tool that integrates with ReSharper
@Dean
I guess we’ll come up with something sweet in the pricing dpt - most probably, a limited-time pricing offer for everyone, and then we’ll see.
@Sergio, @Shannon
dotTrace will integrate with TeamCity but not in the first version unfortunately.
March 24th, 2010 at 3:21 pm
Great news!
At the moment the main coverage tools for .NET are mscoverage, NCover, PartCover so adding a new tool increases choice.
I would like to echo the earlier comments. Is there going to be a command line version and would it have the option of exporting the results as xml? If so will it be bundled for free with TeamCity (the console app so that an agent can easier generate coverage reports)?
Thanks,
John
March 24th, 2010 at 7:13 pm
If this is a separate tool from R#, how is this better than TestDriven.Net?
March 24th, 2010 at 7:23 pm
JetBrains запустит программу раннего доступа к новому инструменту dotCover для Visual Studio…
Thank you for submitting this cool story - Trackback from progg.ru…
March 24th, 2010 at 8:17 pm
Looks exciting. A couple questions:
- Rough estimate of a release date?
- Will there be personal licenses like there are for R# and dotTrace?
- Will there be discounts for people who already use R# or dotTrace?
- Will there be competitive discounts for people who use NCover?
- What customization options will be available in initial release for highlight color / which files are analyzed?
March 25th, 2010 at 3:47 pm
I reiterate others comments for a command-line version with reasonable XML output. Without some sort of headless automation available, it’s value would be diluted. It pains me, then, that you mentioned the possibility of limited-time pricing. I’m not interested in the current feature set but fear I might be priced out when the limited-time pricing expires but the command-line feature is added. Let me also make clear that I’m NOT a TeamCity user, so such specific integration won’t do me any good. Start with a lower common denominator: command-line and XML.
March 26th, 2010 at 2:14 pm
Hi,
EAP will start next week, so many feature-related questions will get answered soon. Version 1.0 will be targeted to individual developers who want to assess quality of their test coverage, so there will not be command-line tool or XML reporting. This will certainly be added veryy soon after 1.0 release and while I can’t share pricing details now, I can assure you that it will answer many concerns expressed here.
WBR, Oleg Stepanov
March 29th, 2010 at 5:48 pm
@Matt
Release date estimate ~ May/June this year
Personal licenses: yes
Discounts for existing R#/dT customers: not sure yet but most probably, there will be an introductory price for all
Discounts for NCover users: this is hardly ethical
Customization options: can’t tell yet.
April 1st, 2010 at 8:51 pm
[...] Access Program for the new JetBrains .NET tool, dotCover! If you missed the news, check out the initial dotCover announcement and Hadi Hariri’s introductory blog post about code coverage for .NET and using [...]
April 23rd, 2010 at 9:37 pm
Just out of curiosity, will this be able to do code-coverage in servers?
We’re having an issue where we’re running “system tests” using MSTest as the framework… these are tests against code in an app-server, doing SOA work. And it would be great to be able to easily get the code-coverage on the server side for the tests written against it.
April 26th, 2010 at 5:37 pm
“Brian J. Sayatovic Says:
March 25th, 2010 at 3:47 pm
I reiterate others comments for a command-line version with reasonable XML output. Without some sort of headless automation available, it’s value would be diluted. It pains me, then, that you mentioned the possibility of limited-time pricing. I’m not interested in the current feature set but fear I might be priced out when the limited-time pricing expires but the command-line feature is added. Let me also make clear that I’m NOT a TeamCity user, so such specific integration won’t do me any good. Start with a lower common denominator: command-line and XML.”
– my sentiments EXACTLY
April 29th, 2010 at 8:22 pm
A couple thoughts:
- Looks like a great product, love the ease of use and integration with Studio
- Repeating other requests for the command line with XML output functionality, necessary for automated builds
- Maybe have an option to just highlight the not-run code - the green highlighting can get annoying and is somewhat redundant. When glancing at highlighted code, the green highlighting is “broken up” by un-compiled code like comments, making coverage seem less than it is at first glance. Ultimately, though, I only care about the un-run code.
- Will it be capable of collecting coverage data outside of a unit test context? Can coverage be collected from manual tests as well?
Thank you.
May 5th, 2010 at 9:03 pm
When will the builds work with Typemock, I cannot evaluate dotCover as my unit tests utilize Typemock ?
Thanks.
p.s. I’ll volunteer to beta test this scenario