Re: Re: comments to JUnit spec

Jaroslav Tulach wrote:
>>No mention here of running individual test methods. This may be possible
>>with Ant 1.7 - follow the RFE in the Ant bug database and think about
>>how we could use it.
> 
> 
> Imho this is P1. I often have test case with a lot of methods and I want to 
> debug the 13th one. I have breakpoints in code and the problem is that before 
> the execution gets to 13th test method, it uselessly stops on them. Of course 
> better usability of debugger would be solution, but the simplest one is to 
> just allow direct execution of individual test method.

I agree this would be very useful. But it is not P1 for NB 4.2. 
Usability of the most basic features (navigation, presentation of 
results) is P1.


> Yes, there is a lot of ways to do to improve productivity and I do not see 
> much of them addressed. 
> 
> Very needed thing is integration with test coverage tool. Be able to run it, 
> present the results in browser or (better) in editor. We have emma 
> integration for NetBeans projects, we should have it for standard j2se ones 
> as well.
> 
> Second direction is making the support really helpful for people who write 
> tests. Jesse mentioned creation of mock objects, I have to second that and 
> I'd like to add that we should come up with direct support writing some of 
> the test patterns[1] we know about: inversion of control, testing AWT like 
> code, randomized tests, layered tests, writing TCKs, logging tests. Those all 
> can be supported with standard junit. We should however also offer advanced 
> features of nbjunit - memory allocation tests, garbage collection tests, 
> algorithm complexity ones. 
> 
> Implementing at least parts of these suggestions would turn the junit support 
> from a nice toy to really useful tool.

These are nice. But for the following release (NB 4.2) I will focus on 
the most painful part of the JUnit module - presentation of results. 
Please bear in mind that I will also work on another modules, so the 
JUnit module will have about 0.6 persons working on it.

Regarding the test patterns, I am not sure how wide audience is eager 
for these features. For now, I do not consider them high priority until 
I improve usability of the most basic features.

Marian