Procedure

Basic Beans Visualization, Parse, and Launch

Import smoke_test_source.zip  into an Eclipse project.  
Open each class in the Visual Editor
Verify that the contents are displayed properly (correct representation of each component and layout).
Launch each class using the Java Bean Launcher and
Verify that the running program matches what is displayed on the canvas.


Basic Beans Inspection

Import codegen_examples.zip into an Eclipse project.
Open AwtComponents.java, BasicSwingComponents.java and MoreSwingComponents.java in the VE and
Verify that each visual bean is displayed properly on the Canvas and that the Beans View hierarchy is correct.  


Run AwtComponents and MoreSwingComponents with the Java Bean Launcher and
Verify they launch properly and display matches the canvas.

Open BasicSwingComponentsBundled.java
Verify the strings are displayed properly - should match what BasicSwingComponents looks like.


Applet Launcher

Open MyApplet.java
From the Run menu, select Run...
Create a new Java Bean / Applet launch configuration
Add the following Applet Parameters:
One -> Hello
Two -> World
Run the launch configuration.
Verify that the applet parameters were passed in correctly.


Basic Functionality Verification

Note: verify generated source after each step to make sure it is valid.

Perform the following tests with on JPanel, JApplet and Frame.
Create a new empty Visual Class and/or extend the container
Change the container's layout to FlowLayout.
Place 5 or more components onto the container.


Change some of the visual properties, such as color, font, border, text, etc. on various components from the property sheet and source
Verify the property editors work properly
Verify the property changes are reflected on all views

Select the container and look at the layout property.
Verify that properties with subproperties have a + to expand sub properties
Verify that subproperties are displayed correctly.
Verify that modifying the gap subproperties for FlowLayout are reflected on all views.

Reorder the components visually and from the source
Verify the components are reordered properly on the canvas, beans view and source.

Change the container's layout to every layout option (null, border, box, card, flow, gridbag, grid) randomly from both the PS and the source.
Verify sure each conversion happens properly.

Select a component on the canvas and MB2->Rename Field.  Change the name of the component.
Verify the source changes properly, the canvas remains unchanged, and the new title is reflected in the beans view.

Save, close and reopen class.
Verify class is loaded and displayed properly.

Make sure you save the JPanel for the next step.

 

Dropping other Visual Beans and Preferences

Create a new Visual Class extending JFrame.
Go to Window->Preferences->Java->Visual Editor and check the options for Generate comment for new expressions and Generate try/catch block
Use the Choose Bean dialog to drop both the Swing panel created in the previous example.  
Verify that the dropped bean appears correctly and that the code generation preferences work

Go back to the VE preferences page, change the Look & Feel and the editors to separate notebook tabs.
Save the file, close and reopen it.
Verify the Look & Feel changes, and the editors are on separate notebook tabs.

Return to the preferences page and turn off any changes you don't care for

 

Non-Visual Beans Test

Create a new empty Visual Class (extend Object)
Import jbcfexamplebeans.zip
Use the Choose Bean dialog to drop a BasicTypes object onto the free form
Verify that the non-visual bean is displayed properly on the free form
Verify that you can modify every value on the Property Sheet to all valid values, and that the non primitives can be set to null.
Verify changes of properties in the source roundtrip.


Primitive Variable Values Test

This tests the ability of codegen to handle primitive variable inputs for properties
Import PrimitiveVariableTest.zip
Open the file test.me.PrimitiveVariableTest.java in the Visual Editor
Verify that the opened file looks like

Verify that the basicTypes bean has all properties set in the propertysheet as coded in the source
Note: an IllegalArgumentException is thrown on the property shortPrim but its value is set correctly in the propertysheet