History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-500
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Steve Luo
Reporter: AlSt
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Ant specific JUnit code can lead to failing pseudo tests that cause subsequent problems in test history tracking

Created: 13/Jan/10 08:50 AM   Updated: 19/Jan/10 09:03 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. XML File tests.xml (7 kb)

Image Attachments:

1. BeforeFirstTest1.png
(81 kb)

2. BeforeFirstTest2.png
(35 kb)

3. BeforeFirstTest3.png
(61 kb)

4. BeforeFirstTest4.png
(40 kb)
Environment: Ant + JUnit


 Description  « Hide
Note: I have submitted an unexpected exception before (cf. attached screenshot #4) -- please ignore that and focus instead on this one.

"BeforeFirstTest" stems from Ant: see http://mail-archives.apache.org/mod_mbox/ant-dev/200607.mbox/%3C20060708211941.792401A981A@eris.apache.org%3E
...
} else if (args[i].startsWith("crashfile=")) {
+ crashFile = args[i].substring(12);
+ registerTestCase("BeforeFirstTest");
...

And presumably the JVM of the JUnit test execution crashed once before, e.g. leading to this error message:
    junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.


 All   Comments   Work Log   Change History      Sort Order:
No work has yet been logged on this issue.