Bug 3839 - funit print meaningfull error messages, not stack backtraces
Summary: funit print meaningfull error messages, not stack backtraces
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Nurdin Premji
URL:
Keywords:
Depends on:
Blocks: 2242
  Show dependency treegraph
 
Reported: 2007-01-06 10:56 UTC by Andrew Cagney
Modified: 2007-01-08 18:42 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2007-01-06 10:56:19 UTC
vis:

./TestRunner frysk.proc.TestAbandon.testAbandonAndAbandonX
Running testAbandonAndAbandonX(frysk.proc.TestAbandon) ...FAIL
  junit.framework.AssertionFailedError: Method "testAbandonAndAbandonX" not found

Time: 0.006
There was 1 failure:
1)
testAbandonAndAbandonX(frysk.proc.TestAbandon)junit.framework.AssertionFailedError:
Method "testAbandonAndAbandonX" not found
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArchCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)

it should print an error message and fail before running any tests.

When it comes to command line programs, error messages at the start, are better
than stack backtraces.
Comment 1 Nurdin Premji 2007-01-08 18:42:25 UTC
Fixed.
January 8, 2007
frysk-imports/frysk/junit/CL
	* Runner.java (runCases): Check that test actually exists before trying to
	run it. Fixes bug #3839.