| Summary: | funit doesn't report bad method names until during test run | ||
|---|---|---|---|
| Product: | frysk | Reporter: | Andrew Cagney <cagney> |
| Component: | general | Assignee: | Unassigned <frysk-bugzilla> |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2242 | ||
(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. |
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