[Bug general/4212] New: funit doesn't report bad method names until during test run

[Bug general/4212] New: funit doesn't report bad method names until during test run

[cagney at redhat dot com]

For instance:

cagney@toidi$ /usr/lib/frysk/funit
'testHitAndRunXXX(frysk.proc.TestBreakpoints)'
'testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)'
Couldn't find method with name: testHitAndRunXXX
Running testSteppingtestHitAndRun(frysk.proc.TestBreakpoints) ...ERROR
  java.lang.NullPointerException

it should have errored before even starting the test run.

There is the code:

                        //Check if the method exists.
                        klass.getMethod(testName, null);
                        
but the lack of any check on status suggests it isn't doing much

-- 
           Summary: funit doesn't report bad method names until during test
                    run
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cagney at redhat dot com
OtherBugsDependingO 2242
             nThis:


http://sourceware.org/bugzilla/show_bug.cgi?id=4212

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/4212] funit doesn't report bad method names until during test run

[mark at klomp dot org]

------- Additional Comments From mark at klomp dot org  2007-03-19 15:36 -------
(In reply to comment #0)
> For instance:
> 
> cagney@toidi$ /usr/lib/frysk/funit
> 'testHitAndRunXXX(frysk.proc.TestBreakpoints)'
> 'testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)'
> Couldn't find method with name: testHitAndRunXXX

testHitAndRun shouldn't be XXX disabled. Or was this just an example?

> Running testSteppingtestHitAndRun(frysk.proc.TestBreakpoints) ...ERROR
>   java.lang.NullPointerException

This should now be fixed in CVS. But I assume this is also not really related to
the core issue of this bug report.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4212

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.