<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="./spec.xsl" ?>

<spec title="Orchestration Roundtrip Test Specification" version="1.2" author = "Victoria Zhukovskaya" author-email="victoriaz@netbeans.org"  last-updated = "08 October 2007">
<intro>This specification provides a usecases for checking Roundtrip engineering in Service Oriented Architecture projects.
</intro>

<!-- The first part: Creating and modifying elements and containers via disigner-->

<caseblock name="Forward Engineering of elements">
	<purpose> Checking that BPEL elements created via disigner have proper XML code</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
        <intro>Should be applied for all elements</intro>
	<usecase name ="Check created element">
		<action>Drag-n-drop any element from Orchestration palette to diagram inside Sequence.</action>
		<action>Select the created element on diagram.</action>
		<action>Switch to Source View.</action>
		<action>Find the newly created element inside Sequence.</action>
		
        <result>Invoked element should be created on diagram inside Sequence.</result>
		<result>Properties window should show element's properies.</result>
		<result>Source View should show XML code of the BPEL process.</result>
		<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.</result>
	</usecase>
	<usecase name ="Check Renamed Element">
        <action>Switch to Design View</action>
		<action>Select the created element on diagram.</action>
        <action>Rename the element by typing a new name in the Properties window.</action>
		<action>Switch to Source View and find the renamed element inside Sequence.</action>
        
		<result>BPEL diagram is shown in the Multi-editor window.</result>
		<result>Properties window should show element's properies.</result>
		<result>Element on the diagram should have the same name as displayed in the Properties window.</result>
		<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.</result>
	</usecase>
	<usecase name ="Check Deleted element">
        <action>Switch to Design View</action>
		<action>Select the renamed element on diagram and press Delete button.</action>
		<action>Switch to Source View and be sure that there is no the renamed element inside Sequence.</action>
        
		<result>BPEL diagram is shown in the Multi-editor window.</result>
		<result>The selected element should be removed from the diagram.</result>
		<result>Source code should not contain tags of the renamed element.</result>
	</usecase>
</caseblock>

<caseblock name="Forward Engineering of Structured Activities">
	<purpose>Checking that Structured Activities created via disigner have proper XML code for all inner elements</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
        <intro>Should be applied for all elements and Structured Activities</intro>
	<usecase name ="Create an element inside Structured Activity">
		<action>Drag-n-drop a Structured Activity from Orchestration palette to diagram inside Sequence.</action>
		<action>Drag-n-drop a element from Orchestration palette to diagram inside Structured Activity.</action>
		<action>Switch to Source View.</action>
		<action>Find the newly created Structured Activity with the newly created element inside.</action>
		
        <result>Invoked Structured Activity should be created on diagram inside Sequence.</result>
        <result>Invoked element should be created on diagram inside Structured Activity.</result>
		<result>Source View should show XML code of the BPEL process.</result>
		<result>Source code should contain tags of the created Structured Activity with a created element.</result>
	</usecase>
	<usecase name ="Add an element into Structured Activity (NOT FOR ALL STRUCTURED ACTIVITIES)">
		<action>Drag-n-drop a element from Orchestration palette to diagram inside Structured Activity.</action>
		<action>Switch to Source View.</action>
		<action>Find the newly created element inside the Structured Activity.</action>
		
        <result>Invoked element should be created on diagram inside Structured Activity.</result>
		<result>Source View should show XML code of the BPEL process.</result>
		<result>Source code should contain tags of the created Structured Activity with an added element.</result>
	</usecase>
	<usecase name ="Remove an element from Structured Activity">
        <action>Switch to Design View</action>
		<action>Select an element inside a Structured Activity and press Delete button.</action>
		<action>Switch to Source View and be sure that there is no deleted element inside the Structured Activity.</action>
		
		<result>BPEL diagram is shown in the Multi-editor window.</result>
		<result>The selected element should be removed from the diagram.</result>
		<result>Source code should contain tags of the Structured Activity without deleted element.</result>
	</usecase>
	<usecase name ="Remove a Structured Activity containing an element">
        <action>Switch to Design View</action>
		<action>Select a Structured Activity which contains an element and press Delete button.</action>
		<action>Switch to Source View and be sure that there are neither Structured Activity nor element which was inside the Structured Activity.</action>
		
		<result>BPEL diagram is shown in the Multi-editor window.</result>
		<result>The selected Structured Activity should be removed from the diagram together with an inner element.</result>
		<result>Source code should not contain tags of the Structured Activity with an inner element.</result>
	</usecase>
</caseblock>

<caseblock name="Moving Elements and Structured Activities">
	<purpose>Checking that moving of Structured Activities or elements in disigner conforms changes in source XML code.</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
        <intro>Should be applied for all elements and Structured Activities</intro>
	<usecase name ="Moving Elements across Structured Activities">
		<action>Drag-n-drop a Structured Activity from Orchestration palette to diagram inside Sequence.</action>
		<action>Drag-n-drop another Structured Activity from Orchestration palette to diagram inside Sequence.</action>
		<action>Drag-n-drop a element from Orchestration palette to diagram inside first Structured Activity.</action>
		<action>Switch to Source View. Find the newly created Structured Activity with the newly created element inside.</action>
        <action>Switch to Design View. Drag-n-drop the element from one Structured Activity to another.</action>
		<action>Switch to Source View. Check changes in the source XML code.</action>
		
        <result>Invoked Structured Activity should be created on diagram inside Sequence.</result>
        <result>One more Structured Activity should be created on diagram inside Sequence.</result>
        <result>Invoked element should be created on diagram inside the first Structured Activity.</result>
		<result>Source code should contain tags of both created Structured Activities with a created element inside one of them.</result>
		<result>The moved element should be placed iside the second Structured Activity.</result>
		<result>Source code should contain tags of both created Structured Activities with the element inside another Structured Activity.</result>
	</usecase>
	<usecase name ="Moving Structured Activity containing an element.">
        <action>Switch to Design View.</action>
        <action>Drag-n-drop a Structured Activity containing an element to the place before (after) another Structured Activity.</action>
        <action>Switch to Source View. Check changes in the source XML code.</action>

		<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.</result>
		<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.</result>
		<result>Source code should contain tags of both created Structured Activities in proper order with the element inside the original Structured Activity.</result>
	</usecase>
</caseblock>

<caseblock name="Adding and modifying Handlers">
	<purpose>Checking that Handlers created via disigner have proper XML code for all inner elements</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
	<!--usecase name ="Create a Compensation Handler">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Add Compensation Handler" context menu item.</action>
        <action>Switch to Source View. Check changes in the source XML code.</action>
		<action>Switch to Disign View. Drag-n-drop a element from Orchestration palette to diagram inside Compensation Handler.</action>
        <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Compensation Handler element appears on the diagram.</result>
		<result>Source code should contain empty tags of a Compensation Handler element inside Process.</result>
        <result>Invoked element should be created on diagram inside Compensation Handler.</result>
		<result>Source code should contain newly created element tags inside Compensation Handler tags.</result>
	</usecase-->
	<!--usecase name ="Create an Event Handlers">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Add Event Handlers" context menu item.</action>
        <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Event Handlers element appears on the diagram.</result>
		<result>Source code should contain empty tags of an Event Handlers element inside Process.</result>
	</usecase-->
	<usecase name ="Create a Fault Handlers">
        <action>Right-click on the Process element on the diagram.</action>
    <action>Choose the "Add" > "Fault Handlers" context menu item.</action>
        <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Add, Go To Source, Properties.</result>
		<result>Fault Handlers element appears on the diagram.</result>
		<result>Source code should contain empty tags of an Fault Handlers element inside Process.</result>
	</usecase>
</caseblock>

<!-- The second part: Creating and modifying variables and properties via disigner -->
<caseblock name="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.</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
	<usecase name ="Changing the Process Name">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Properties" context menu item.</action>
        <action>Enter a new process name and press OK button.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Add, Go To Source, Properties.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>Process element on the diagram has the new name.</result>
		<result>Process element in the source XML code has the new name.</result>
	</usecase>
        <!--
	<usecase name ="Changing the Suppress Join Failure property">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Property Editor" context menu item.</action>
        <action>Set the Suppress Join Failure checkbox and press OK button.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>
	    <action>Set suppressJoinFailure attribute value to "no".</action>	    
	    <action>Switch to Source View. Select the Process element on the diagram.</action>	    

		<result>Context menu appears and contains following items: Property Editor, Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>Process OrchestrationProject-Properties window has Suppress Join Failure checkbox set in the Expert section.</result>
		<result>Process element in the source XML code has an attribute suppressJoinFailure="yes".</result>
		<result>Process element in the source XML code has an attribute suppressJoinFailure="no".</result>
		<result>Process OrchestrationProject-Properties window has Suppress Join Failure checkbox resetted in the Expert section.</result>
	</usecase>
	<usecase name ="Changing the Enable Instance Compensation property">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Property Editor" context menu item.</action>
        <action>Set the Enable Instance Compensation checkbox and press OK button.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>
	    <action>Set enableInstanceCompensation attribute value to "no".</action>	    
	    <action>Switch to Source View. Select the Process element on the diagram.</action>	    

		<result>Context menu appears and contains following items: Property Editor, Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>Process OrchestrationProject-Properties window has Enable Instance Compensation checkbox set in the Expert section.</result>
		<result>Process element in the source XML code has an attribute enableInstanceCompensation="yes".</result>
		<result>Process element in the source XML code has an attribute enableInstanceCompensation="no".</result>
		<result>Process OrchestrationProject-Properties window has Enable Instance Compensation checkbox resetted in the Expert section.</result>
	</usecase>
	<usecase name ="Changing the Abstract Process property">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Property Editor" context menu item.</action>
        <action>Set the Abstract Process checkbox and press OK button.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>
	    <action>Set abstractProcess attribute value to "no".</action>	    
	    <action>Switch to Source View. Select the Process element on the diagram.</action>	    

		<result>Context menu appears and contains following items: Property Editor, Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>Process OrchestrationProject-Properties window has Abstract Process checkbox set in the Expert section.</result>
		<result>Process element in the source XML code has an attribute abstractProcess="yes".</result>
		<result>Process element in the source XML code has an attribute abstractProcess="no".</result>
		<result>Process OrchestrationProject-Properties window has Abstract Process checkbox resetted in the Expert section.</result>
	</usecase-->
</caseblock>

<caseblock name="Forward Engineering of Variables">
	<purpose>Checking that XML source code contains all changes which were made with variables via property editor in design view.</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
	<usecase name ="Add a new variable">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Add" > "Variable..." context menu item.</action>
        <action>Enter a variable name choose the variable type then press OK button.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Add, Go To Source, Properties.</result>
		<result>"Create New Variable" window appears.</result>
		<result>Type of the variable can be chosen through the Type Chooser window.</result>
		<result>Variables section in the source XML code contains the newly created variable of selected type.</result>
	</usecase>
	<usecase name ="Edit an existing variable">
        <action>Switch to Design view then select the Process element on the diagram.</action>
        <action>Right-click on the variable in navigator window  and choose the "Edit" context menu item.</action>
        <action>Enter a new variable name and choose a new variable type then press OK button.</action>
       <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Navigator window has the variable in BPEL Logical View.</result>
		<result>Property Editor window appears.</result>
		<result>Type of the variable can be chosen through the Type Chooser window.</result>
		<result>Variables section in the source XML code contains the renamed variable of new type and does not contain old variable.</result>
	</usecase>
	<usecase name ="Delete an existing variable">
        <action>Switch to Design view then select the Process element on the diagram.</action>
        <action>Right-click on the variable in navigator window  and choose the "Delete" context menu item.</action>
        <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Navigator window has the variable in BPEL Logical View.</result>
		<result>Variable disappears from the BPEL Logical View.</result>
		<result>Variables section in the source XML code does not contain the deleted variable.</result>
	</usecase>
</caseblock>

<!--
<caseblock name="Forward Engineering of Properties">
	<purpose>Checking that XML source code contains all changes which were made with properties via property editor in design view.</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
	<usecase name ="Add a new property">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Property Editor" context menu item.</action>
        <action>Switch to the Properties tab and press the "Add..." button.</action>
        <action>Enter a property name choose the property type then press OK button and once more OK to close the Property Editor.</action>
	    <action>Open OrchestrationProject.wsdl and check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Property Editor, Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>"Create New Correlation Property" window appears.</result>
		<result>Type of the property can be chosen through the Type Chooser window.</result>
		<result>WSDL file contains the newly created property of selected type.</result>
	</usecase>
	<usecase name ="Edit an existing property">
        <action>Open Design view then Right-click on the Process element on the diagram.</action>
        <action>Choose the "Property Editor" context menu item.</action>
        <action>Switch to the Properties tab Select a property then press the "Edit..." button.</action>
        <action>Enter a new property name and choose a new property type then press OK button and once more OK to close the Property Editor.</action>
	    <action>Open OrchestrationProject.wsdl and check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Property Editor, Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>"Edit Correlation Property" window appears.</result>
		<result>Type of the property can be chosen through the Type Chooser window.</result>
		<result>WSDL file contains the renamed property of new type and does not contain old property.</result>
	</usecase>
	<usecase name ="Delete an existing property">
        <action>Open Design view then Right-click on the Process element on the diagram.</action>
        <action>Choose the "Property Editor" context menu item.</action>
        <action>Switch to the Properties tab Select a property then press the "Delete" button.</action>
        <action>Press OK button to close the Property Editor. Open OrchestrationProject.wsdl and check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Property Editor, Add Compensation Handler, Add Event Handlers, Add Fault Handlers.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>Property disappears from the table.</result>
		<result>WSDL file does not contain the deleted property.</result>
	</usecase>
</caseblock>
-->

<caseblock name="Forward Engineering of Correlation Sets">
	<purpose>Orchestaration project has a propery in wsdl-file.</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in design view. Properties window is open.</setup>
	<usecase name ="Add a new Correlation Set">
        <action>Right-click on the Process element on the diagram.</action>
        <action>Choose the "Add" > "Correlation Set..." context menu item.</action>
        <action>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.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Context menu appears and contains following items: Add, Go To Source, Properties.</result>
		<result>"Add Correlation Set" window appears.</result>
		<result>Properties to be added to the set can be chosen through the Property Chooser window.</result>
		<result>correlationSets section in the source XML code contains the newly created correlation set of selected properties.</result>
	</usecase>
	<usecase name ="Edit an existing Correlation Set">
        <action>Switch to Design view then select the Process element on the diagram.</action>
        <action>Right-click on the Correlation Set in navigator window  and choose the "Edit" context menu item.</action>
        <action>Enter a new correlation set name and add remove or modify included properties then press OK button.</action>
	    <action>Switch to Source View. Check changes in the source XML code.</action>

		<result>Navigator window has the Correlation Set in BPEL Logical View.</result>
		<result>Property Editor window appears and shows Main tab.</result>
		<result>Properties to be added to the set can be chosen through the Property Chooser window.</result>
		<result>correlationSets section in the source XML code contains the renamed correlation set of modified property set.</result>
	</usecase>
	<usecase name ="Delete an existing Correlation Set">
        <action>Switch to Design view then select the Process element on the diagram.</action>
        <action>Right-click on the Correlation Set in navigator window  and choose the "Delete" context menu item.</action>
        <action>Press OK button to close the Property Editor. Switch to Source View. Check changes in the source XML code.</action>

		<result>Navigator window has the Correlation Set in BPEL Logical View.</result>
		<result>The Correlation Set disappears from the BPEL Logical View.</result>
		<result>correlationSets section in the source XML code does not contain the deleted correlation set.</result>
	</usecase>
</caseblock>

<!-- The third part: Creating and modifying elements via source code -->
<caseblock name="Reverse Engineering of elements">
	<purpose> Checking that BPEL elements created in XML source is displayed properly in design view</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in source view. Properties window is open.</setup>
        <intro>Should be applied for all elements</intro>
	<usecase name ="Check created element">
		<action>Create an element in the source editor according BPEL specification. Save changes.</action>
		<action>Switch to Design view.</action>
		<action>Select the newly created element on diagram to check its properties.</action>
		<action>Modify some property then switch to Source View to check modified property.</action>
		
        <result>A new element is created in source code inside Sequence. XML should be checked and validated successfully.</result>
        <result>Created element should appear on diagram inside Sequence.</result>
		<result>Properties window should show element's properies.</result>
		<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.</result>
	</usecase>
	<usecase name ="Check Deleted element">
		<action>Delete an element in the source editor. Save changes</action>
        <action>Switch to Design View. Check the diagram.</action>
        
		<result>The piece of code containing element does not exist. XML should be checked and validated successfully.</result>
		<result>The deleted element should be removed from the diagram.</result>
	</usecase>
</caseblock>

<caseblock name="Reverse Engineering of Structured Activities">
	<purpose>Checking that Structured Activities created  in XML source is displayed properly in design view with all inner elements.</purpose>
        <setup>A new Orchestration project is created and open in the Multi-view editor in source view. Properties window is open.</setup>
        <intro>Should be applied for all elements and Structured Activities</intro>
	<usecase name ="Create an element inside Structured Activity">
		<action>Create a Structured Activity in the source editor according BPEL specification.</action>
		<action>Create an element in the Structured Activity in the source editor according BPEL specification. Save changes.</action>
		<action>Switch to Design view. Find the newly created Structured Activity with the newly created element inside.</action>
		<action>Select the Structured Activity with the newly created element inside.</action>
		
        <result>A new Structured Activity element is created in source code inside Sequence.</result>
        <result>A new element is created in source code inside the Structured Activity element. XML should be checked and validated successfully.</result>
        <result>Created Structured Activity with inner element should appear on diagram inside Sequence.</result>
		<result>Properties window should show element's properies. Values of properties should be the same as in source code.</result>
	</usecase>
	<usecase name ="Add an element into Structured Activity (NOT FOR ALL STRUCTURED ACTIVITIES)">
		<action>Create an element in the Structured Activity in the source editor according BPEL specification. Save changes.</action>
		<action>Switch to Design view. Find the Structured Activity with the newly created element inside.</action>
		<action>Select the newly created element inside the Structured Activity.</action>
		
        <result>A new element is created in source code inside the Structured Activity element. XML should be checked and validated successfully.</result>
        <result>Created element should appear on diagram inside the Structured Activity.</result>
		<result>Properties window should show element's properies. Values of properties should be the same as in source code.</result>
	</usecase>
	<usecase name ="Remove an element from Structured Activity">
        <action>Switch to Source View</action>
		<action>Select an element code lines inside a Structured Activity and press Delete button. Save changes.</action>
		<action>Switch to Design View and be sure that there is no deleted element inside the Structured Activity.</action>
		
		<result>XML BPEL source is shown in the source editor window.</result>
		<result>The selected element code lines should be removed from the source. XML should be checked and validated successfully.</result>
		<result>Diagram should contain the Structured Activity without deleted element.</result>
	</usecase>
	<usecase name ="Remove a Structured Activity containing an element">
        <action>Switch to Source View</action>
		<action>Select a Structured Activity element code lines which and press Delete button. Save changes.</action>
		<action>Switch to Design View and be sure that there is no deleted Structured Activity.</action>
		
		<result>XML BPEL source is shown in the source editor window.</result>
		<result>The selected Structured Activity should be removed from the source code. XML should be checked and validated successfully.</result>
		<result>Diagram should not contain deleted Structured Activity with an inner element.</result>
	</usecase>
</caseblock>

<caseblock name="Reverse Engineering of Partner Links">
	<purpose>Checking that Partner Links modified in WSDL is displayed properly in design view.</purpose>
        <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.</setup>
	<usecase name ="Add an operation to the Partner Link">
		<action>Switch to the opened Project WSDL file and find "wsdl:portType" section.</action>
		<action>Copy one of existing operation and paste it with another name. Save changes.</action>
		<action>Switch to Design view. Find the PartnerLink element.</action>
		
        <result>The portType section should show existing operation for the certain port.</result>
        <result>The portType section should contain a new operation.</result>
        <result>The newly created operaton should appear inside the Partner Link element.</result>
	</usecase>
	<usecase name ="Remove an operation from the Partner Link">
		<action>Switch to the opened Project WSDL file and find "wsdl:portType" section.</action>
		<action>Remove one of existing operation from the souce. Save changes.</action>
		<action>Switch to Design view. Find the PartnerLink element.</action>
		
        <result>The portType section should show existing operation for the certain port.</result>
        <result>The portType section should not contain the removed operation.</result>
        <result>The removed operaton should disappear from the Partner Link element.</result>
	</usecase>
</caseblock>

</spec>
