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

Bug 345577

Summary: Decorators do not show Active/Inactive Status quickly enough in large projects
Product: [Technology] Jubula Reporter: Oliver Goetz <Oliver.Goetz>
Component: UIAssignee: Markus Tiede <markus.tiede>
Status: CLOSED FIXED QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: critical    
Priority: P1 CC: Achim.Loerke, alexandra.schladebeck, markus.tiede
Version: 0.9.0   
Target Milestone: Indigo SR1   
Hardware: All   
OS: Windows Server 2008   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=355379
https://bugs.eclipse.org/bugs/show_bug.cgi?id=355382
Whiteboard:
Attachments:
Description Flags
Active/Inactive decorator fails
none
SC active/inactive none

Description Oliver Goetz CLA 2011-05-12 06:51:24 EDT
Created attachment 195487 [details]
Active/Inactive decorator fails

There still seems to a problem with the decorators. 
Exemplification:

 * Select a TS in TSB and expand tree to single TCs
 * Open the TS in TSE
 * Select one of the TCs included in the TS and change its status e.g. to inactive 
 * Now select both TC
 * When quickly pressing ctrl+7 to change the status of both TCs between active/inactive at some point you can notice that the status is not changed
 * Save the TS in TSE so it is not dirty
 * The status of the TCs is different comparing the TSB and TSB (check attached screenshot) and not refreshed when saving the TS in TSE
 * It seems that the TSB shows the correct status of the TCs

Workaround:

Press F5 to refresh the whole project.
Comment 1 Oliver Goetz CLA 2011-07-13 08:40:43 EDT
Switching between active/inactive status in large projects is not displayed immediately after changing the status

Prerequisites:
 * Open a large project (e.g. GUIdancer_5.2)
 * Open a TC and switch its status (active/inactive)

The status change is not displayed immediately after switching. It takes some time until you can see that the status has been changed. A refresh does not help. The status change is neither displayed in the TCB nor the TCE or TSB and changes only in the TSB and TCB after waiting some time. Tested with GD for Windows and Unix using the GUIdancer_5.2 project. Using a smaller project (e.g. Samples) the status change is displayed immediately.
Comment 2 Oliver Goetz CLA 2011-07-13 08:46:40 EDT
Created attachment 199575 [details]
SC active/inactive
Comment 3 Alexandra Schladebeck CLA 2011-08-22 07:20:08 EDT
I am increasing the priority of this issue, as it leads to confusion when working with larger projects. An action is performed that leads to a status change that should be shown in the GUI and the new status isn't shown. This has already lead to tests being incorrectly committed as they are commented out, but should not be.
Comment 4 Alexandra Schladebeck CLA 2011-08-30 10:08:29 EDT
When this bug is closed, please also close the following:
https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=109
Comment 5 Markus Tiede CLA 2011-09-09 03:07:29 EDT
*** Bug 355384 has been marked as a duplicate of this bug. ***
Comment 6 Markus Tiede CLA 2011-09-09 04:07:53 EDT
The performance issue should be fixed with

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=e93f209672882218e7ab08368aa86d0180497c70
Comment 7 Alexandra Schladebeck CLA 2011-09-13 06:35:53 EDT
The status of the decoration is now shown once the save has completed. 
Tested by commenting out a centrally used module in a large project and checking that the status is updated in the Test Case Browser and Test Suite Browser.
Comment 8 Alexandra Schladebeck CLA 2011-09-13 07:25:55 EDT
Although the problem with changing the comment status quickly still exists, I think that this is more of a theoretical problem now. If anyone *does* change the comment status of items repeatedly in quick succession, then the GUI can show different statuses for the editor and browsers. However, toggling the active/inactive status of the item in the editor and saving puts the GUI back into the correct state. 

For this reason, I am closing the bug as successfully fixed.