This specification provides test cases description for testing the BPEL Refactoring feature in the NB 5.5 Enterprise Pack release. Test how refactoring in upstream artifacts affects the BPEL process. Start the IDE. Open the test project Open TestXmlSchema document in editor Find and select complex type element ComplexTypeAlpha in editor Invoke Refactor->Rename command for element Proceed to perform the Rename operation Variable declaration in diagram should be updated There should not be any changes in the diagram All usages of the complex type should be renamed Complex type usages should be renamed in Navigator Open the test project Find and select complex type element ComplexTypeAlpha in editor Invoke Find Usages command for element IDE should find 2 complex type usages in process scope IDE should find complex type usage in process nested scope Open the test project Open TestXmlSchema document in editor Find and select schema element named SchemaElement in editor Invoke Refactor->Rename command for element Proceed to perform the Rename operation Variable declaration in diagram should be updated There should not be any changes in the diagram All usages of the element type should be renamed Element type usages should be renamed in Navigator Open the test project Find and select schema element SchemaElement in editor Invoke Find Usages command for element IDE should find 2 schema element usages in process scope IDE should find schema element usage in process nested scope Open the test project Open TestXmlSchema document in editor Find and select schema element TestSimpleType editor Invoke Refactor->Rename command for element Proceed to perform the Rename operation Variable declaration in diagram should be updated There should not be any changes in the diagram All usages of the simple type should be renamed Element type usages should be renamed in Navigator Open the test project Find and select schema element TestSimpleType in editor Invoke Find Usages command for element IDE should find 2 schema simple type usages in process scope IDE should find schema simple type usage in process nested scope Open the test project Open TestXmlSchema document in editor Find and select nested element ParamA under RootComplexType element Invoke Refactor->Rename command for element Proceed to perform the Rename operation There should not be any changes in the diagram All usages of the nested type in XPath expressions should be renamed Element type usages should be renamed in Navigator Open the test project Open TestXmlSchema document in editor Find and select schema nested element RootComplexType in editor Invoke Find Usages command for element Usage of nested element in If activity should be found 2 Usages of nested element in Assign activity should be found Usage of nested element in While activity should be found Usage of nested element in RepeatUntil activity should be found Test how refactoring in upstream artifacts affects the BPEL process. Start the IDE. Open the test project Open process wsdl file in wsdl designer Find and select the requestMessage message Click Find Usages in the context menu IDE should find message usage in the variable declaration IDE should find message usage in the faultHandler declaration IDE should find message usage in the property alias in wsdl file IDE should find message usage in the input1 parameter in wsdl file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the requestMessage message Click Refactor->Rename in the context menu Proceed to perform the rename operation IDE should rename message usage in the variable declaration IDE should rename message usage in the faultHandler declaration IDE should rename message usage in the property alias in wsdl file IDE should rename message usage in the input1 parameter in wsdl file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the Messages->requestMessage->inputType message Click Find Usages in the context menu IDE should find message usage in the EventHandlers->AlarmHandler->For IDE should find message usage in the EventHandlers->AlarmHandler->Until IDE should find message usage in the assignment IDE should find message usage in the Pick->AlarmHandler->For IDE should find message usage in the Pick->AlarmHandler->Until IDE should find message usage in the Wait IDE should find message usage in the If IDE should find message usage in the Else-If IDE should find message usage in the While IDE should find message usage in the RepeatUntil IDE should find message usage in the Foreach (3 usages) IDE should find message usage in the property alias in wsdl file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the Messages->requestMessage->inputType message Click Find Usages in the context menu IDE should rename message usage in the EventHandlers->AlarmHandler->For IDE should rename message usage in the EventHandlers->AlarmHandler->Until IDE should rename message usage in the assignment IDE should rename message usage in the Pick->AlarmHandler->For IDE should rename message usage in the Pick->AlarmHandler->Until IDE should rename message usage in the Wait IDE should rename message usage in the If IDE should rename message usage in the Else-If IDE should rename message usage in the While IDE should rename message usage in the RepeatUntil IDE should rename message usage in the Foreach (3 usages) IDE should rename message usage in the property alias in wsdl file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the Port Types->PortType1->operation1->testFault Click Find Usages in the context menu IDE should find message usage in the Reply declaration IDE should find message usage in the faultHandler declaration IDE should find message usage in the Throw declaration IDE should find message usage in the operation1 in wsdl file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the Port Types->PortType1->operation1->testFault Click Refactor->Rename in the context menu IDE should rename message usage in the Reply declaration IDE should rename message usage in the faultHandler declaration IDE should rename message usage in the Throw declaration IDE should rename message usage in the operation1 in wsdl file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the testProperty property Click Find Usages in the context menu IDE should find property usage in the Correlation set declaration IDE should find property usage in the WSDL document (it's declaration) IDE should find property alias usage in the WSDL document There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the testProperty property Click Refactor->Rename in the context menu IDE should rename property usage in the Correlation set declaration IDE should rename property usage in the WSDL document (it's declaration) IDE should rename property alias usage in the WSDL document There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the portType1 node Click Find Usages in the context menu IDE should find portType usage in the onEvent EventHandler declaration IDE should find portType usage in the Receive declaration IDE should find portType usage in the Reply declaration IDE should find portType usage in the Invoke declaration IDE should find portType usage in the MessageHandler declaration IDE should find portType usage in the WSDL document partner link role (it's declaration) IDE should find portType usage in the binding1 in the WSDL document There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the portType1 node Click Refactor->Rename in the context menu IDE should rename portType usage in the onEvent EventHandler declaration IDE should rename portType usage in the Receive declaration IDE should rename portType usage in the Reply declaration IDE should rename portType usage in the Invoke declaration IDE should rename portType usage in the MessageHandler declaration IDE should rename portType usage in the WSDL document partner link role (it's declaration) IDE should rename portType usage in the binding1 in the WSDL document There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the Port Types->portType1->operation1 node Click Find Usages in the context menu IDE should find operation usage in the onEvent EventHandler declaration IDE should find operation usage in the Receive declaration IDE should find operation usage in the Reply declaration IDE should find operation usage in the Invoke declaration IDE should find operation usage in the MessageHandler declaration IDE should find operation usage in the binding1 in the WSDL document There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the Port Types->portType1->operation1 node Click Refactor->Rename in the context menu IDE should rename operation usage in the onEvent EventHandler declaration IDE should rename operation usage in the Receive declaration IDE should rename operation usage in the Reply declaration IDE should rename operation usage in the Invoke declaration IDE should rename operation usage in the MessageHandler declaration IDE should rename operation usage in the binding1 in the WSDL document There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the BPEL Extensibility Elements->partnerlinktype node Click Find Usages in the context menu IDE should find type usage in the first partnerLink declaration IDE should find type usage in the second partnerLink declaration IDE should find type usage in the WSDL file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the BPEL Extensibility Elements->partnerlinktype node Click Refactor->Rename in the context menu IDE should rename type usage in the first partnerLink declaration IDE should rename type usage in the second partnerLink declaration IDE should rename type usage in the WSDL file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the BPEL Extensibility Elements->partnerlinktype->partnerlinktyperole1 node Click Find Usages in the context menu IDE should find role usage in the partnerLink declaration IDE should find role usage in the WSDL file There should be no more usages in the BPEL-specific artifacts Open the test project Open process wsdl file in wsdl designer Find and select the BPEL Extensibility Elements->partnerlinktype->partnerlinktyperole1 node Click Refactor->Rename in the context menu IDE should rename role usage in the partnerLink declaration IDE should rename role usage in the WSDL file There should be no more usages in the BPEL-specific artifacts Test that renaming artifacts in BPEL designer renames all the usages of the artifact Start the IDE. Open the sample project Open the test project Open BPEL process in designer Rename inputVar variable to inputVar1 Rename outputVar variable to outputVar1 There should not be any changes in the diagram All usages of the variables should be renamed Variables should be renamed in Navigator Open the test project Open BPEL process in designer Rename inputVar variable to inputVar1 Rename outputVar variable to outputVar1 There should not be any changes in the diagram All usages of the variables should be renamed. String literals equal to variable names should not be renamed Variables should be renamed in Navigator Open the test project Open BPEL process in designer Find myCorrealtionSet correlation set in Navigator, choose Edit in context menu Rename myCorrelationSet to myCorrelationSet1 There should not be any changes in the diagram All correlation set usages should be renamed in Navigator All correlation set usages should be renamed in sources Open the test project Open BPEL process in designer Open partnerLinkA editor by double clicking on the activity Rename partner link partnerLinkA to partnerLinkA1 Open partnerLinkB editor by double clicking on the activity Rename partner link partnerLinkB to partnerLinkB1 There should not be any changes in the diagram except the changed activities names In source all usages of partnerLinkA should be renamed to partnerLinkA1 In source all usages of partnerLinkB should be renamed to partnerLinkB1