| |
| WebLogic Workshop™ Control Validation Program Compatibility Specification |
|
 |
| The Compatibility Specification for Workshop Java Controls (Controls) was developed by BEA to identify Controls that run successfully within BEA Weblogic Workshop 8.1 (Workshop). This specification will help software developers by defining the minimum requirements for Java Controls to operate within Workshop. |
|
 |
 |
|
| |
BEA Validated™
This specification does not include deep functionality testing of the Extension, its integration with back-end services, or any testing designed to make Extensions more robust and manageable. It is intended to test:
|
• The Control will install into Workshop smoothly
• The Control is functionally sound and has design time compatibility with Workshop
• The Control ships with end user HTML based help pages which integrate with the Workshop Help System
• The Control ships with detailed samples using the control with Workshop Web Services, Page Flows, and Java Process Documents
• The Control will be unlikely to cause Workshop to crash or collide with other vendor files
• Customers will have instructions on uninstalling the Extension
|
The testing process essentially follows this workflow:
|
• Examination of Control Deliverable - verify that it is signed correctly, structured correctly, free from virus, etc.
• Control Installation - “Right-click Install” succeeds; all components/help files/etc installed in the correct locations.
• Test insert of control instance in JWS - Control appears on insert menu with custom icon and label; instance declaration has all required annotations to compile without errors.
• Test Insert Wizard (if applicable) - Required for controls that create JCX files. Supply valid and invalid values to control-supplied entry fields; verify compile without errors.
• Test help integration - Verify that pressing on an instance declaration launches javadoc help; verify pressing on custom property of a control launches control-tag help files.
• If control creates a JCX, attempt to create a stand alone JCX via File New Control.
• Verify that jc-jar.xml file has correct / appropriate entries.
• Follow any instructions supplied with sample applications and verify that they can compile and run once without errors.
• Test Control Wizards (if applicable) - Verify that wizards conform to UI specifications for size, multiple pages, etc.
|
|
|
The complete testing requirements are available here: Control Test Plan.
|
You may also download these requirements in PDF format here: BEA_Control_Test_Plan.pdf.
|
|
| |
|
| |
To submit your product for BEA Validation please use the Validation Submission Form, or for more information, please contact us. |
|