Form Editor - Property Editors Test Specification

Author: Jaromir Uhrik
Version: 1.0.1
Last update: 24.05.2004
Introduction: This is intended as tests of Property Editors from Form module.
Comment:

Table of Contents

• 1. Form module Property Editors tests

Test suite 1: Form module Property Editors tests Purpose: Test proper behaviour of property editors. Setup: Start IDE with clear userdir - default MDI mode is set. # Test case Description 1 Border 1. Add JPanel to Form. 2. Select property border. 3. Try all kinds of border: No Border BevelBorder CompoundBorder EmptyBorder EtchedBorder LineBorder MatteBorder TitledBorder 4. Change some properties for borders. 5. Check generated code for all kinds of border. 6. Change border editor to Form Connection (by combo box). 7. Type user code. 8. Check generated code. RESULT: All borders work properly. 2 ComboBox model 1. Add JComboBox to form. 2. Open property editor for property model. 3. Try add items, remove items, change orders of items. RESULT: Properly generated code. 3 Cursor 1. Select Top Container. 2. Select property cursor. 3. Try change cursors and check it in generated code. RESULT: 4 List Model 1. Add JList. 2. Open property editor for property model. 3. Try add items, remove items, change orders of items. RESULT: Properly generated code. 5 Accelerator 1. Add JMenu. 2. Add JmenuItem to JMenu. 3. Select property accelerator. 4. Change property - try Ctrl, Shift, Alt. RESULT: Properly generated code. 6 Mnemonic 1. Add JMenu. 2. Add JmenuItem to JMenu. 3. Select property mnemonic. 4. Try set mnemonic, try set more than one char. RESULT: Properly generated code. 7 Custom code 1. Add JButton to form. 2. Select tab Code generation. 3. Select property Post-Creation Code. 4. Insert own code. 5. Your code is added to generated code. 6. Try all properties with own code. RESULT: Properly generated code. 8 Enum 1. Select tab Code generation. 2. Change property Form Size Policy. RESULT: Properly generated code. 9 Event ustom editor 1. Add JButton. 2. Select tab Events. 3. Select property editor for event actionPerformed. 4. Add handlers h1, h2. 5. Try remove handlers, add handlers, rename handlers. 6. Select property editor for event ancestorAdded. 7. Add handlers h1, h3. 8. You get exception for handlers h1. 9. Select property editor for event ancestorMoved. 10. Add handlers h3, h4. RESULT: Properly behaviour, properly generated code. Teardown:

---

Generated: Mon May 24 10:52:51 CEST 2004