10 comments
Comment actions Permalink

I'd be more than willing to kick in for some muffins, if it would get the nifty new code coverage UI stuff on my desktop. It's getting so that I hate seeing reports of feature requests fulfilled, because I know it's gonna be another week 'til I actually get my hands on 'em.

--Dave Griffith

0
Comment actions Permalink

Hello Dave,

DG> I'd be more than willing to kick in for some muffins, if it would
DG> get the nifty new code coverage UI stuff on my desktop. It's
DG> getting so that I hate seeing reports of feature requests fulfilled,
DG> because I know it's gonna be another week 'til I actually get my
DG> hands on 'em.

No EAP for the next couple of days at least - too many things broken here...

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Damn, I feel anxious about your feedback on code coverage UI:) We still have to decide whether code coverage shall be chosen from combobox in the toolbar, or should we invent some other UI for that. I'll appreciate all suggestions.

0
Comment actions Permalink

It's ok, I'll wait for a couple of days as long as we can build testng plugin against idea.jar (obfuscator issues) and the code coverage is available in all run dialogs, not just the junit one ;)

0
Comment actions Permalink

Those new UI solutions might actually be well known ones:
a) Popup menu accessible from Main Menu | View | Code Coverage
b) Quick-switch style popup

or both...

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Damn, I feel anxious about your feedback on code coverage UI:) We
still have to decide whether code coverage shall be chosen from
combobox in the toolbar, or should we invent some other UI for that.
I'll appreciate all suggestions.



0
Comment actions Permalink

Still it would be preferrable to see for what test suite the coverage information is displayed. Any suggestion for such visualization?

0
Comment actions Permalink

Hmmm, on one hand, the toolbar has the big advantage that new users will actually see it. Otherwise, there's a real risk of someone buying 6.0 and never even realizing that it includes a code coverage tool. On the other hand, "which coverage run do I want to look at" isn't something that I want to change all that often. The answer is going to be "the full unit test suite I set up" about 95% of the time.

Under the "View" menu would be doable, although either "Analyze" or "Run" would also make sense. Hurm, it's a "View"-like interaction for "Analyze"-like data created by a "Run". Best to go with "View", if you want a main menu solution.

Oh, and whatever you choose, you should display the run configuration name, rather than the name of the package/class for the test run. I actually take the effort to name my run configs (and will do so even more thoroughly now that they can be shared! yay!), and there's no reason to ignore those names.

And finally, stop worrying! The underlying code coverage tech you've come up with is great, and the only real problems are that it was a pain to turn on or get rollup data from. That means I literally can't get enough of it now!

--Dave Griffith

0
Comment actions Permalink

One comment I'd made in another thread mentioning this which didn't seem to generate a response was getting JB to email either me or you copies of the ModuleBasedRunConfiguration (and dependant classes) so that we could (momentarrily untill they get open officially, or the build problems go away) graft them into our codebase.

That'd at least get the plugin compilable/releasable and make alot of people happy...

0
Comment actions Permalink

Well, you could of course neglect giving me some virtual beer, but ModuleBasedConfiguration is opened along with its dependent classes:)

0
Comment actions Permalink

w00t - bring on the builds :)

As for beer - I have vodka right next me....

0

Please sign in to leave a comment.