Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355379 - Renamed nodes are not updated quickly enough in larger projects
Summary: Renamed nodes are not updated quickly enough in larger projects
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P2 major (vote)
Target Milestone: Indigo SR1   Edit
Assignee: Markus Tiede CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-22 08:45 EDT by Alexandra Schladebeck CLA
Modified: 2011-09-15 06:10 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandra Schladebeck CLA 2011-08-22 08:45:58 EDT 
When a node is renamed (either by adding a new Referenced Test Case Name to a reused Test Case, or using F2 on a node in a browser), the displayed name in the GUI is not updated. This effect is noticeable in larger projects (I was using the GUIdancer 5.2 project). The name is shown correctly after refreshing the project, but refreshing a project after each rename is not a comfortable workaround.
Comment 1 Markus Tiede CLA 2011-09-09 04:08:25 EDT 
The performance / refresh issue should be fixed with

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=e93f209672882218e7ab08368aa86d0180497c70
Comment 2 Alexandra Schladebeck CLA 2011-09-13 07:11:50 EDT 
Verified: Performance and refresh are both better.