Output Window in Test Runner

Thanks to Tomas Holy who provided an API for embedding the output window component, we now have clickable links and all the other goodies that the OW component provides in the Ruby test runner:

Another enhancement which you can see above is the result bar for showing the percentage of passed tests (thanks to Tor for that component). Both of these improvements are actually also in the JUnit, PHP and Python test runners since they are all using the same common test runner API.

Comments:

Nice additions.

A pre-existing issue for me is that the error window is a bit too small.

It would be nice to have the left results window and the right error window in seperate movable tabs.

Or better yet maybe an icon next to each FAIL that slides out a bigger error window when clicked.

Posted by DK on March 10, 2009 at 04:44 PM CET #

Hi DK,

Thanks for the comment. There is a couple of things you can try to make the error window bigger: you can drag the test results component away from the group it is in by default, i.e. so that it extends all the way from left to right (of course, this layout will eat space from the left where the navigator window is by default). Also, when you run tests you see the same output also in the actual output window, so with a bit of playing with the layout you should be able to have the OW and the test runner window visible at the same time. Then you can just minimize the output component in the test runner window. Finally, if you drag around the test runner window so that it is vertical, it will automatically switch its layout. Though not sure whether that will be of any use to you.

That said, all the above solutions have some drawbacks; you're right that it would be nice to have something like you suggest.

Posted by Erno Mononen on March 11, 2009 at 01:58 AM CET #

Looks nice! Something I really miss from Jbuilder is the test runner. I could right click a single failed test case and rerun it. In NB 6.5 I have to rerun the whole test class which is a waste of time. Is the real problem Ant? Jbuilder used it’s own test runner but is NB only presenting what Ant is returning?

Posted by Roger P on March 11, 2009 at 03:19 AM CET #

Hi Roger,
Yes, I think Ant makes it difficult to implement running a single test for JUnit. In 6.5 re-running a single JUnit test should already be supported for some project types, hopefully for all the project types in 6.7 -- you can track the progress on this <a href="http://www.netbeans.org/issues/show_bug.cgi?id=72080">IZ 72080</a> (note I don't really have much insight on this as I don't work on the JUnit test runner). Being able to run and re-run a single test case is definitely the single feature I miss most in the JUnit runner. We have the feature for various Ruby testing frameworks though, but that is obviously rather thin solace when working with Java projects.

Posted by Erno Mononen on March 11, 2009 at 04:27 AM CET #

Running unit tests is poor for Java in NetBeans. It seems OK for Ruby now but why not Java? I can't decide whether I should stop doing Java and write Ruby in NetBeans or keep doing Java but make a change to Eclipse. Maybe a new version will make it better for Java.

Posted by Srinivas M. on March 11, 2009 at 08:43 AM CET #

Hi Srinivas,
In 6.7 there will be several improvements also in the JUnit runner, for example the OW component I blogged about is there for JUnit as well (though it may not have hyperlinked output as of now, but that should be fixed before 6.7 final).

Posted by Erno Mononen on March 12, 2009 at 02:14 AM CET #

Post a Comment:
Comments are closed for this entry.
About

emononen's blog

Search

Top Tags
Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today