This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 22008 - Verify newly implemented Undo/Redo support in the GUI editor
Summary: Verify newly implemented Undo/Redo support in the GUI editor
Status: RESOLVED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Richard Malaschitz
URL:
Keywords:
Depends on: 21415 21483 21486
Blocks: 21650
  Show dependency tree
 
Reported: 2002-04-01 19:19 UTC by Jan Chalupa
Modified: 2004-09-03 14:58 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Chalupa 2002-04-01 19:19:02 UTC
There will be a new Undo/Redo support in the GUI editor:
http://www.netbeans.org/issues/show_bug.cgi?id=21415

Verify that the feature works as specified
http://www.netbeans.org/issues/show_bug.cgi?id=21483

Also make sure that no regressions were introduced by the 
new implementation. If appropriate, extend the existing 
Form acceptance test specification with new test cases for 
Undo/Redo.
Comment 1 Tomas Pavek 2002-04-02 16:26:32 UTC
Some notes about what needs to be tested...

These are the operations for which undo/redo should work:
- adding a new component,
- removing (deleting) a component,
- copying components - copy/paste, cut/paste; both within
  one form and between different forms; also copying
  of "instances" (from Explorer to form),
- drag&drop - within one container, and between containers,
- changing a bean property of component,
- changing a synthetic (code generation) property,
- changing layout of a container,
- changing a property of container layout,
- changing a property of component layout constraints,
- changing a bean or layout property together with
  property editor,
- components reordering,
- adding a new event handler,
- attaching a component event to existing event handler,
- deleting an event handler,
- detaching a component event from event handler
  (being used for multiple events),
- renaming an event handler.

All the changes need to be tested separately for undo and 
redo; two times at least (like undo, redo, undo, redo). 
Also check some sequences of usual operations (note the 
undo queue is limited to 50 changes now).

Both the designer and the generated code need to be 
checked after each change.

Compound operation should be tested separately - they must 
be undone/redone as a whole (for one undo/redo 
invocation). These are mainly operations with multiple 
components (deleting, copying, drag&drop, changing 
properties, changing events). Deleting is a compound 
operation even for one component (mainly if it is a 
container or if it has events attached).
Comment 2 Marek Grummich 2002-07-22 11:27:10 UTC
Set target milestone to TBD
Comment 3 Jan Chalupa 2004-09-03 14:58:03 UTC
Obsolete.