Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 158284

Summary: Test Log Viewer: Issues when the view is open during a test execution.
Product: z_Archived Reporter: Paul Slauenwhite <paulslau>
Component: TPTPAssignee: Paul Slauenwhite <paulslau>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P2 CC: chenbs, eejessee, flannanl, paulslau
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: housecleaned462
Bug Depends on: 273121    
Bug Blocks:    

Description Paul Slauenwhite CLA 2006-09-22 07:56:08 EDT
NullPointerException when running a test with the Test Log viewer open.

When running a manual test using the TPTP-4.3.0-200609200100 driver with the Test Log viewer open, the following NullPointerException is thrown when the test execution completes forcing the user to re-open the Test Log viewer to see the remaining execution results:

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
	at org.eclipse.swt.SWT.error(SWT.java:3374)
	at org.eclipse.swt.SWT.error(SWT.java:3297)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:615)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by: java.lang.NullPointerException
	at org.eclipse.hyades.test.ui.forms.editor.BaseFormEditor.reload(BaseFormEditor.java:516)
	at org.eclipse.hyades.test.ui.forms.editor.BaseFormEditor.editorFileChanged(BaseFormEditor.java:485)
	at org.eclipse.hyades.test.ui.forms.editor.TestLogViewer.editorFileChanged(TestLogViewer.java:62)
	at org.eclipse.hyades.ui.internal.editor.EditorSynchronizer$2.run(EditorSynchronizer.java:404)
	at org.eclipse.hyades.ui.internal.editor.EditorSynchronizer$SynchronizedRunnable.run(EditorSynchronizer.java:90)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
	... 20 more
Comment 1 Paul Slauenwhite CLA 2006-10-23 10:50:34 EDT
Please target to 4.4 and review the priority according to http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html.
Comment 2 Paul Slauenwhite CLA 2006-11-01 10:31:38 EST
ACTION ITEM:  Please target to 4.4 and review the priority according to
http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html by the end of 4.3 i3 (Friday, November 3, 2006).
Comment 3 Paul Slauenwhite CLA 2007-01-17 09:17:43 EST
Sizing updated as provided by Bianaca.
Comment 4 Paul Slauenwhite CLA 2007-01-26 08:28:39 EST
Targeting to future since cannot be contained in 4.4.
Comment 5 Paul Slauenwhite CLA 2007-01-26 08:33:38 EST
Targeting to future since cannot be contained in 4.4.
Comment 6 Paul Slauenwhite CLA 2007-01-26 09:01:27 EST
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4.  All other Test Project defects have been targeted to future.

If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org).  We will collectively triage and assess our resources to determine a case-by-case decision. 
Comment 7 Paul Slauenwhite CLA 2007-01-26 09:03:45 EST
Correction:  The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Comment 8 Paul Slauenwhite CLA 2007-11-07 10:18:23 EST
Reassigning to the Project Lead.
Comment 9 Paul Slauenwhite CLA 2008-05-27 08:09:34 EDT
*** Bug 134562 has been marked as a duplicate of this bug. ***
Comment 10 Paul Slauenwhite CLA 2008-05-27 08:09:51 EDT
In addition:

[Defect #153617]
Execution events are not refreshed in the Test Log viewer

I have a handler which opens the Test Log viewer right after the test is
launched. When the viewer opens, I expect that the viewer will be refreshed
whenever a new execution event is generated. However, all I see is the root
event in the viewer and I need to click the "Expand" button to refresh the
viewer manually.

[Defect #134562]
Missing execution events when the Test Log View is open during a test
execution.

When the Test Log View is open during a test execution (e.g. running a manual
test), only the start, stop and invocation events are displayed in the Events
tab of the view (see attached screen capture).  The user has to close/reopen
the view to display the complete tree of execution events.

1) Launch a manual test.
2) Open the Test Log viewer to the Events tab.
3) Run the manual test to completion.

Screen capture: https://bugs.eclipse.org/bugs/attachment.cgi?id=37547
Comment 11 Paul Slauenwhite CLA 2008-05-27 08:10:01 EDT
*** Bug 153617 has been marked as a duplicate of this bug. ***
Comment 12 Paul Slauenwhite CLA 2008-05-27 08:15:50 EDT
In addition, when adding a new defect to an event in the Test Log View and saving the test log, the event tree collapses and the navigation buttons do not iterate the event tree.  The user has to close/re-open the test log view to use the navigation buttons.
Comment 13 Paul Slauenwhite CLA 2008-05-29 09:15:29 EDT
Mistakenly targeted to 4.5i8 so targeting back to future.
Comment 14 Paul Slauenwhite CLA 2008-07-10 10:24:37 EDT
We will need to handle updating the Verdict Summary and Verdict List sections of the Overview tab as the events are being loaded (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=187337).
Comment 15 Paul Slauenwhite CLA 2008-07-11 08:29:26 EDT
In addition:

[Defect #114638]
Test Log Viewer: Verdict navigation toolbar buttons do not enable/disable correctly.

If Test log viewer is opened before the test finishes executing, the verdict 
navigation toolbar (enabled/disabled) status reflects the verdicts contained 
when the log is opened. While test log viewer refreshes when there's changes 
to the content of test log, toolbar status doesn't.
Comment 16 Ben Chen CLA 2009-06-25 13:55:19 EDT
in tptp 4.6 (driver: TPTP-4.6.0-200906191311)
If a test is being ran and the test log is opened in its editor, the verdicts are updated as the test execution goes along.
I don't see the problem in the description.
Comment 17 Ben Chen CLA 2009-06-25 14:30:15 EDT
(In reply to comment #10)
> In addition:
> 
> [Defect #153617]
> Execution events are not refreshed in the Test Log viewer
> 
> I have a handler which opens the Test Log viewer right after the test is
> launched. When the viewer opens, I expect that the viewer will be refreshed
> whenever a new execution event is generated. However, all I see is the root
> event in the viewer and I need to click the "Expand" button to refresh the
> viewer manually.
> 
> [Defect #134562]
> Missing execution events when the Test Log View is open during a test
> execution.
> 
> When the Test Log View is open during a test execution (e.g. running a manual
> test), only the start, stop and invocation events are displayed in the Events
> tab of the view (see attached screen capture).  The user has to close/reopen
> the view to display the complete tree of execution events.
> 
> 1) Launch a manual test.
> 2) Open the Test Log viewer to the Events tab.
> 3) Run the manual test to completion.
> 
> Screen capture: https://bugs.eclipse.org/bugs/attachment.cgi?id=37547
> 

To be more precise:

whenever the test execution finishes with one test case, the verdict of that test case is updated and shown in the logviewer(Events tab) accordingly, although in the Overview tab, the chart and the verdict list does not refresh until log is re-opened.
Comment 18 Ben Chen CLA 2009-06-25 14:43:06 EDT
(In reply to comment #12)
> In addition, when adding a new defect to an event in the Test Log View and
> saving the test log, the event tree collapses and the navigation buttons do not
> iterate the event tree.  The user has to close/re-open the test log view to use
> the navigation buttons.
> 

After trying with this scenario, it seems the event tree remain it's previous status if a defect number is added to one of the verdicts during test execution, also the navigation issue remains as noted in comment #12

If a defect number is added to one of the verdicts AFTER: test execution/testlog has already been generated, then the event tree will collapse. Navigation function working as designed.
Comment 19 Ben Chen CLA 2009-06-25 14:44:38 EDT
(In reply to comment #14)
> We will need to handle updating the Verdict Summary and Verdict List sections
> of the Overview tab as the events are being loaded (see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=187337).
> 

issue still exists, see comment #17
Comment 20 Ben Chen CLA 2009-06-25 15:04:28 EDT
(In reply to comment #15)
> In addition:
> 
> [Defect #114638]
> Test Log Viewer: Verdict navigation toolbar buttons do not enable/disable
> correctly.
> 
> If Test log viewer is opened before the test finishes executing, the verdict 
> navigation toolbar (enabled/disabled) status reflects the verdicts contained 
> when the log is opened. While test log viewer refreshes when there's changes 
> to the content of test log, toolbar status doesn't.
> 

Navigation seems limited to the verdicts generated prior to opening the test log before execution finishes.
Comment 21 Paul Slauenwhite CLA 2009-06-30 07:00:31 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Comment 22 Paul Slauenwhite CLA 2009-07-02 15:21:57 EDT
Reopening since still relevant.
Comment 23 Paul Slauenwhite CLA 2010-03-10 12:18:35 EST
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Comment 24 Paul Slauenwhite CLA 2010-03-25 20:01:50 EDT
Closing.