Bug 4212 - funit doesn't report bad method names until during test run
Summary: funit doesn't report bad method names until during test run
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 2242
  Show dependency tree / graph
 
Reported: 2007-03-19 14:31 UTC by Andrew Cagney
Modified: 2007-03-19 15:36 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2007-03-19 14:31:46 UTC 
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
Comment 1 Mark Wielaard 2007-03-19 15:36:57 UTC 
(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.