Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350594 - Test Result Export fails - no export-file written
Summary: Test Result Export fails - no export-file written
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: Indigo SR1   Edit
Assignee: Oliver Goetz CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-28 11:00 EDT by Andreas CLA
Modified: 2011-09-27 06:09 EDT (History)
1 user (show)

See Also:


Attachments
Log File Embedded DB (1.91 KB, text/plain)
2011-07-06 06:54 EDT, Oliver Goetz CLA
no flags Details
Log File Oracle (1.90 KB, text/plain)
2011-07-06 06:55 EDT, Oliver Goetz CLA
no flags Details
Log File PostGreSQL (1.91 KB, text/plain)
2011-07-06 06:55 EDT, Oliver Goetz CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas CLA 2011-06-28 11:00:01 EDT
Build Identifier: 0.9.0.qualifier

For certain (longish) test-suites no test result can be exported they reproducably fail with a NullPointerException like this:

2011-06-28 16:42:56.011 [main] ERROR o.e.j.c.u.w.ExportTestResultDetailsWizard - Error occurred while exporting Test Result details.
java.lang.NullPointerException: null
	at org.eclipse.jubula.client.core.businessprocess.AbstractXMLReportGenerator.addCapElement(AbstractXMLReportGenerator.java:271) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.AbstractXMLReportGenerator.buildElement(AbstractXMLReportGenerator.java:210) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.CompleteXMLReportGenerator.buildElement(CompleteXMLReportGenerator.java:57) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.CompleteXMLReportGenerator.buildElement(CompleteXMLReportGenerator.java:60) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.CompleteXMLReportGenerator.buildElement(CompleteXMLReportGenerator.java:60) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.CompleteXMLReportGenerator.buildElement(CompleteXMLReportGenerator.java:60) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.CompleteXMLReportGenerator.buildElement(CompleteXMLReportGenerator.java:60) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.AbstractXMLReportGenerator.buildRootElement(AbstractXMLReportGenerator.java:164) ~[na:na]
	at org.eclipse.jubula.client.core.businessprocess.CompleteXMLReportGenerator.generateXmlReport(CompleteXMLReportGenerator.java:42) ~[na:na]
	at org.eclipse.jubula.client.ui.wizards.ExportTestResultDetailsWizard$ExportTestResultDetailsOperation.run(ExportTestResultDetailsWizard.java:142) ~[na:na]
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) ~[na:na]

The export wizard shows up, performs a quick 0 to 100% progression, then closes. No file is written. 

The bug occurs for every execution of the test-suite. The bug occurs after refresh and and after restart. Other test-suites perform as expected (produce reports).
The test-project uses a Postgres DBMS.


Reproducible: Always

Steps to Reproduce:
1. Execute Testsuite
2. Open Functional Test Reporting
3. Select test in Test Result Summary
4. Right-click on test, choose 'Export' from context-menu
5. Select existing destination
6. Press 'Finish'-Button
Comment 1 Achim Loerke CLA 2011-06-29 03:11:56 EDT
@Oliver: please try to build a reproducible test in our environment, attach log files from failures.
Comment 2 Oliver Goetz CLA 2011-07-06 06:54:10 EDT
Created attachment 199173 [details]
Log File Embedded DB
Comment 3 Oliver Goetz CLA 2011-07-06 06:54:50 EDT
I was able to reproduce this error. I used the samples project imported on three different DBs (Oracle, PostGreSQL and the embedded DB), ran every testsuite and tried to export the test result summaries. The test result summaries for the SA TS (every toolkit) were all exported, the test result summaries for the DVD Tool and the Meters Tool were not exported no matter which DB was used. Maybe this is connected with the length of TS since the SA TS only consist of a few TCs (mostly 4) and the DVDTool and Meters TS are much longer. This issue does not seem to be connected with the use of different DBs since this error occured on every DB used. For further info check the attached client log files for the Meters TS.
Comment 4 Oliver Goetz CLA 2011-07-06 06:55:30 EDT
Created attachment 199174 [details]
Log File Oracle
Comment 5 Oliver Goetz CLA 2011-07-06 06:55:56 EDT
Created attachment 199175 [details]
Log File PostGreSQL
Comment 6 Oliver Goetz CLA 2011-08-31 06:05:50 EDT
This is a duplicate of https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=90
Comment 7 Oliver Goetz CLA 2011-09-27 06:09:32 EDT
Closed as fixed (see https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=90)