comments to JUnit spec

Radim Kubacki <[email protected]>
Newsgroups gmane.comp.java.netbeans.user-interface
Message-ID <[email protected]>
I did not get any response neither from author nor from
[email protected] so I am resending to nbui.

-Radim

Hi all,

I have a few comments to http://ui.netbeans.org/docs/ui/junits/promo_f.html

The most important one: we are too much focused on test creating. IMO
the test is created once and then it is sometimes updated during
development and it should be run often.

Why do we have a dialog & wizard? Cannot we reuse one UI for all cases?

Goto test case/source - dealing with more tests for one method contained
under different test roots sounds cool but it will be pretty rare IMO
and we should focus on more important things (just one some of these tests).

Orphaned tests - either these tests really have a value and should be
kept or their out-of-date state will be revealed at next run test
invocation.

Context menus - it is good to hear that we are going to remove tools
action org/netbeans/modules/junit/TestsAction. I like this idea. I would
like to remind you that there is no project window context menu. Each
object type can have a different context menu. Placing of this action in
the editor menu at the top is to courageous. It is not the most
important action in the editor navigation.

JUnit options - I do not know how it fits into options redesign effort.

The section about results is the shortest one and a lot of things is
mising here (and in other sections too). Should the execution of tests
use progress bar? It apparently takes some time. You have proposed more
tabs that I would like to see and did not pay attention how the failures
/ errors / successes will be presented - plain text or formatted output.
How can I navigate to source code / test code from a failure? How to
rerun (only) failed test?

BTW: Rudo, can you use numbered list next time to make it easier to
comment the document?

-Radim
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.