TS 61 BPELRoundTrip

Orchestration Roundtrip Test Specification

Author: Victoria Zhukovskaya
Version: 1.2
Last update: 08 October 2007
Introduction: This specification provides a usecases for checking Roundtrip engineering in Service Oriented Architecture projects.


Comments:


Contents


Test suite: Forward Engineering of elements

Purpose: Checking that BPEL elements created via disigner have proper XML code
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Check created element
    1. Drag-n-drop any element from Orchestration palette to diagram inside Sequence.
    2. Select the created element on diagram.
    3. Switch to Source View.
    4. Find the newly created element inside Sequence.
    • EXPECTED RESULT: Invoked element should be created on diagram inside Sequence.
    • EXPECTED RESULT: Properties window should show element's properies.
    • EXPECTED RESULT: Source View should show XML code of the BPEL process.
    • EXPECTED RESULT: Source code should contain tags of the created element and the value of the attribute "name" for the element should be the same as it was shown in the Properties window.
  1. Check Renamed Element
    1. Switch to Design View
    2. Select the created element on diagram.
    3. Rename the element by typing a new name in the Properties window.
    4. Switch to Source View and find the renamed element inside Sequence.
    • EXPECTED RESULT: BPEL diagram is shown in the Multi-editor window.
    • EXPECTED RESULT: Properties window should show element's properies.
    • EXPECTED RESULT: Element on the diagram should have the same name as displayed in the Properties window.
    • EXPECTED RESULT: Source code should contain tags of the renamed element and the value of the attribute "name" for the element should be the same as it appeared in the Properties window.
  1. Check Deleted element
    1. Switch to Design View
    2. Select the renamed element on diagram and press Delete button.
    3. Switch to Source View and be sure that there is no the renamed element inside Sequence.
    • EXPECTED RESULT: BPEL diagram is shown in the Multi-editor window.
    • EXPECTED RESULT: The selected element should be removed from the diagram.
    • EXPECTED RESULT: Source code should not contain tags of the renamed element.


Test suite: Forward Engineering of Structured Activities

Purpose: Checking that Structured Activities created via disigner have proper XML code for all inner elements
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Create an element inside Structured Activity
    1. Drag-n-drop a Structured Activity from Orchestration palette to diagram inside Sequence.
    2. Drag-n-drop a element from Orchestration palette to diagram inside Structured Activity.
    3. Switch to Source View.
    4. Find the newly created Structured Activity with the newly created element inside.
    • EXPECTED RESULT: Invoked Structured Activity should be created on diagram inside Sequence.
    • EXPECTED RESULT: Invoked element should be created on diagram inside Structured Activity.
    • EXPECTED RESULT: Source View should show XML code of the BPEL process.
    • EXPECTED RESULT: Source code should contain tags of the created Structured Activity with a created element.
  1. Add an element into Structured Activity (NOT FOR ALL STRUCTURED ACTIVITIES)
    1. Drag-n-drop a element from Orchestration palette to diagram inside Structured Activity.
    2. Switch to Source View.
    3. Find the newly created element inside the Structured Activity.
    • EXPECTED RESULT: Invoked element should be created on diagram inside Structured Activity.
    • EXPECTED RESULT: Source View should show XML code of the BPEL process.
    • EXPECTED RESULT: Source code should contain tags of the created Structured Activity with an added element.
  1. Remove an element from Structured Activity
    1. Switch to Design View
    2. Select an element inside a Structured Activity and press Delete button.
    3. Switch to Source View and be sure that there is no deleted element inside the Structured Activity.
    • EXPECTED RESULT: BPEL diagram is shown in the Multi-editor window.
    • EXPECTED RESULT: The selected element should be removed from the diagram.
    • EXPECTED RESULT: Source code should contain tags of the Structured Activity without deleted element.
  1. Remove a Structured Activity containing an element
    1. Switch to Design View
    2. Select a Structured Activity which contains an element and press Delete button.
    3. Switch to Source View and be sure that there are neither Structured Activity nor element which was inside the Structured Activity.
    • EXPECTED RESULT: BPEL diagram is shown in the Multi-editor window.
    • EXPECTED RESULT: The selected Structured Activity should be removed from the diagram together with an inner element.
    • EXPECTED RESULT: Source code should not contain tags of the Structured Activity with an inner element.


Test suite: Moving Elements and Structured Activities

Purpose: Checking that moving of Structured Activities or elements in disigner conforms changes in source XML code.
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Moving Elements across Structured Activities
    1. Drag-n-drop a Structured Activity from Orchestration palette to diagram inside Sequence.
    2. Drag-n-drop another Structured Activity from Orchestration palette to diagram inside Sequence.
    3. Drag-n-drop a element from Orchestration palette to diagram inside first Structured Activity.
    4. Switch to Source View. Find the newly created Structured Activity with the newly created element inside.
    5. Switch to Design View. Drag-n-drop the element from one Structured Activity to another.
    6. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Invoked Structured Activity should be created on diagram inside Sequence.
    • EXPECTED RESULT: One more Structured Activity should be created on diagram inside Sequence.
    • EXPECTED RESULT: Invoked element should be created on diagram inside the first Structured Activity.
    • EXPECTED RESULT: Source code should contain tags of both created Structured Activities with a created element inside one of them.
    • EXPECTED RESULT: The moved element should be placed iside the second Structured Activity.
    • EXPECTED RESULT: Source code should contain tags of both created Structured Activities with the element inside another Structured Activity.
  1. Moving Structured Activity containing an element.
    1. Switch to Design View.
    2. Drag-n-drop a Structured Activity containing an element to the place before (after) another Structured Activity.
    3. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: BPEL diagram is shown in the Multi-editor window. There are two Structured Activities inside the Sequence. One of the Structured Activities contains an element.
    • EXPECTED RESULT: Drag-n-drop of the Structured Activity succeeeds. The Structured Activity with the inner element moved to the place before (after) another Structured Activity.
    • EXPECTED RESULT: Source code should contain tags of both created Structured Activities in proper order with the element inside the original Structured Activity.


Test suite: Adding and modifying Handlers

Purpose: Checking that Handlers created via disigner have proper XML code for all inner elements
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Create a Fault Handlers
    1. Right-click on the Process element on the diagram.
    2. Choose the "Add" > "Fault Handlers" context menu item.
    3. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Context menu appears and contains following items: Add, Go To Source, Properties.
    • EXPECTED RESULT: Fault Handlers element appears on the diagram.
    • EXPECTED RESULT: Source code should contain empty tags of an Fault Handlers element inside Process.


Test suite: Forward Engineering of the Process via Property Editor

Purpose: Checking that XML source code contains all changes which were made in process via property editor in design view.
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Changing the Process Name
    1. Right-click on the Process element on the diagram.
    2. Choose the "Properties" context menu item.
    3. Enter a new process name and press OK button.
    4. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Context menu appears and contains following items: Add, Go To Source, Properties.
    • EXPECTED RESULT: Property Editor window appears and shows Main tab.
    • EXPECTED RESULT: Process element on the diagram has the new name.
    • EXPECTED RESULT: Process element in the source XML code has the new name.


Test suite: Forward Engineering of Variables

Purpose: Checking that XML source code contains all changes which were made with variables via property editor in design view.
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Add a new variable
    1. Right-click on the Process element on the diagram.
    2. Choose the "Add" > "Variable..." context menu item.
    3. Enter a variable name choose the variable type then press OK button.
    4. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Context menu appears and contains following items: Add, Go To Source, Properties.
    • EXPECTED RESULT: "Create New Variable" window appears.
    • EXPECTED RESULT: Type of the variable can be chosen through the Type Chooser window.
    • EXPECTED RESULT: Variables section in the source XML code contains the newly created variable of selected type.
  1. Edit an existing variable
    1. Switch to Design view then select the Process element on the diagram.
    2. Right-click on the variable in navigator window and choose the "Edit" context menu item.
    3. Enter a new variable name and choose a new variable type then press OK button.
    4. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Navigator window has the variable in BPEL Logical View.
    • EXPECTED RESULT: Property Editor window appears.
    • EXPECTED RESULT: Type of the variable can be chosen through the Type Chooser window.
    • EXPECTED RESULT: Variables section in the source XML code contains the renamed variable of new type and does not contain old variable.
  1. Delete an existing variable
    1. Switch to Design view then select the Process element on the diagram.
    2. Right-click on the variable in navigator window and choose the "Delete" context menu item.
    3. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Navigator window has the variable in BPEL Logical View.
    • EXPECTED RESULT: Variable disappears from the BPEL Logical View.
    • EXPECTED RESULT: Variables section in the source XML code does not contain the deleted variable.


Test suite: Forward Engineering of Correlation Sets

Purpose: Orchestaration project has a propery in wsdl-file.
Setup: A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.

  1. Add a new Correlation Set
    1. Right-click on the Process element on the diagram.
    2. Choose the "Add" > "Correlation Set..." context menu item.
    3. Enter a Correlation Set name and press Add button then choose a property to be added to set then press OK button and once more OK.
    4. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Context menu appears and contains following items: Add, Go To Source, Properties.
    • EXPECTED RESULT: "Add Correlation Set" window appears.
    • EXPECTED RESULT: Properties to be added to the set can be chosen through the Property Chooser window.
    • EXPECTED RESULT: correlationSets section in the source XML code contains the newly created correlation set of selected properties.
  1. Edit an existing Correlation Set
    1. Switch to Design view then select the Process element on the diagram.
    2. Right-click on the Correlation Set in navigator window and choose the "Edit" context menu item.
    3. Enter a new correlation set name and add remove or modify included properties then press OK button.
    4. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Navigator window has the Correlation Set in BPEL Logical View.
    • EXPECTED RESULT: Property Editor window appears and shows Main tab.
    • EXPECTED RESULT: Properties to be added to the set can be chosen through the Property Chooser window.
    • EXPECTED RESULT: correlationSets section in the source XML code contains the renamed correlation set of modified property set.
  1. Delete an existing Correlation Set
    1. Switch to Design view then select the Process element on the diagram.
    2. Right-click on the Correlation Set in navigator window and choose the "Delete" context menu item.
    3. Press OK button to close the Property Editor. Switch to Source View. Check changes in the source XML code.
    • EXPECTED RESULT: Navigator window has the Correlation Set in BPEL Logical View.
    • EXPECTED RESULT: The Correlation Set disappears from the BPEL Logical View.
    • EXPECTED RESULT: correlationSets section in the source XML code does not contain the deleted correlation set.


Test suite: Reverse Engineering of elements

Purpose: Checking that BPEL elements created in XML source is displayed properly in design view
Setup: A new Orchestration project is created and open in the Multi-view editor in source view. Properties window is open.

  1. Check created element
    1. Create an element in the source editor according BPEL specification. Save changes.
    2. Switch to Design view.
    3. Select the newly created element on diagram to check its properties.
    4. Modify some property then switch to Source View to check modified property.
    • EXPECTED RESULT: A new element is created in source code inside Sequence. XML should be checked and validated successfully.
    • EXPECTED RESULT: Created element should appear on diagram inside Sequence.
    • EXPECTED RESULT: Properties window should show element's properies.
    • EXPECTED RESULT: Source code should contain tags of the created element and the value of the modified attribute should be the same as it was shown in the Properties window.
  1. Check Deleted element
    1. Delete an element in the source editor. Save changes
    2. Switch to Design View. Check the diagram.
    • EXPECTED RESULT: The piece of code containing element does not exist. XML should be checked and validated successfully.
    • EXPECTED RESULT: The deleted element should be removed from the diagram.


Test suite: Reverse Engineering of Structured Activities

Purpose: Checking that Structured Activities created in XML source is displayed properly in design view with all inner elements.
Setup: A new Orchestration project is created and open in the Multi-view editor in source view. Properties window is open.

  1. Create an element inside Structured Activity
    1. Create a Structured Activity in the source editor according BPEL specification.
    2. Create an element in the Structured Activity in the source editor according BPEL specification. Save changes.
    3. Switch to Design view. Find the newly created Structured Activity with the newly created element inside.
    4. Select the Structured Activity with the newly created element inside.
    • EXPECTED RESULT: A new Structured Activity element is created in source code inside Sequence.
    • EXPECTED RESULT: A new element is created in source code inside the Structured Activity element. XML should be checked and validated successfully.
    • EXPECTED RESULT: Created Structured Activity with inner element should appear on diagram inside Sequence.
    • EXPECTED RESULT: Properties window should show element's properies. Values of properties should be the same as in source code.
  1. Add an element into Structured Activity (NOT FOR ALL STRUCTURED ACTIVITIES)
    1. Create an element in the Structured Activity in the source editor according BPEL specification. Save changes.
    2. Switch to Design view. Find the Structured Activity with the newly created element inside.
    3. Select the newly created element inside the Structured Activity.
    • EXPECTED RESULT: A new element is created in source code inside the Structured Activity element. XML should be checked and validated successfully.
    • EXPECTED RESULT: Created element should appear on diagram inside the Structured Activity.
    • EXPECTED RESULT: Properties window should show element's properies. Values of properties should be the same as in source code.
  1. Remove an element from Structured Activity
    1. Switch to Source View
    2. Select an element code lines inside a Structured Activity and press Delete button. Save changes.
    3. Switch to Design View and be sure that there is no deleted element inside the Structured Activity.
    • EXPECTED RESULT: XML BPEL source is shown in the source editor window.
    • EXPECTED RESULT: The selected element code lines should be removed from the source. XML should be checked and validated successfully.
    • EXPECTED RESULT: Diagram should contain the Structured Activity without deleted element.
  1. Remove a Structured Activity containing an element
    1. Switch to Source View
    2. Select a Structured Activity element code lines which and press Delete button. Save changes.
    3. Switch to Design View and be sure that there is no deleted Structured Activity.
    • EXPECTED RESULT: XML BPEL source is shown in the source editor window.
    • EXPECTED RESULT: The selected Structured Activity should be removed from the source code. XML should be checked and validated successfully.
    • EXPECTED RESULT: Diagram should not contain deleted Structured Activity with an inner element.


Test suite: Reverse Engineering of Partner Links

Purpose: Checking that Partner Links modified in WSDL is displayed properly in design view.
Setup: A new Orchestration project is created and open in the Multi-view editor in source view. Properties window is open. Project WSDL file is open in editor.

  1. Add an operation to the Partner Link
    1. Switch to the opened Project WSDL file and find "wsdl:portType" section.
    2. Copy one of existing operation and paste it with another name. Save changes.
    3. Switch to Design view. Find the PartnerLink element.
    • EXPECTED RESULT: The portType section should show existing operation for the certain port.
    • EXPECTED RESULT: The portType section should contain a new operation.
    • EXPECTED RESULT: The newly created operaton should appear inside the Partner Link element.
  1. Remove an operation from the Partner Link
    1. Switch to the opened Project WSDL file and find "wsdl:portType" section.
    2. Remove one of existing operation from the souce. Save changes.
    3. Switch to Design view. Find the PartnerLink element.
    • EXPECTED RESULT: The portType section should show existing operation for the certain port.
    • EXPECTED RESULT: The portType section should not contain the removed operation.
    • EXPECTED RESULT: The removed operaton should disappear from the Partner Link element.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo