| << Back to previous view |
|
[QB-500] Ant specific JUnit code can lead to failing pseudo tests that cause subsequent problems in test history tracking
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | AlSt | Assigned To: | Steve Luo |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Ant + JUnit | ||
| File Attachments: |
BeforeFirstTest1.png
BeforeFirstTest2.png
BeforeFirstTest3.png
BeforeFirstTest4.png
tests.xml
|
| Description |
|
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/%[email protected]%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. |
| Comments |
| Comment by AlSt [ 13/Jan/10 08:55 AM ] |
| From qb20\storage\builds\136040\reports\junit\DEFAULT: this shows why I think it is a test history problem |
| Comment by AlSt [ 13/Jan/10 09:23 AM ] |
|
Note: After the next run this problem has gone again -- most likely because the history/trend is only shown between two consecutive builds.
=> Thus, I would say the priority of this issue should be lower, i.e. normal. |