Organizations often use Oracle alongside other Enterprise Resource Planning (ERP) applications like Salesforce and Workday. These integrations create workflows that require testing across various applications. Traditional testing tools struggle with such scenarios due to the inherent differences in each application's interface and functionalities. Opkey simplifies integration testing, especially for complex workflows that span multiple applications.
Opkey achieves this through specialized keywords that instruct the testing tool to switch between applications based on the workflow steps.
This article explores how Opkey facilitates integration testing, using a common scenario of creating a quotation on Salesforce and then generating a corresponding sales order in Oracle.
Hover over the Automate section and select Test.
Since the workflow given above involves both Salesforce and Oracle, using the same plugin for the entire test case won't work. To ensure proper execution, you'll need to add the "Set Generic Plugin" keyword in the end of Salesforce component (or first component). This keyword instructs Opkey to switch to the Oracle Fusion plugin (or next component of the flow) for the subsequent steps.
Now, open your ERP component to add the SetGenericPlugin keyword. Here, we are opening our Salesforce pre-built component to create a quotation. If you don't have pre-built components, you can create new reusable components for your ERP workflows and them call them in a new test case.Note: If your integrated workflow first executes Oracle's steps followed by steps of other ERP, then you must add the SetGenericPlugin keyword in the Oracle reusable component. This will enable the execution agent to first run Oracle's steps and then switch plugin to execute steps of your ERP workflow.
Add the keyword after the last step in the Salesforce component. You can find it by searching within Opkey's keyword options.
Select the last step of your component and click the Add Step button at the top. This will add a new step in the end of this reusable component.
4. After adding the step, search SetGenericPlugin keyword and add it into the step.
5. This keyword takes plugin name as input. During execution, it switches the plugin to enable steps after it to execute with the new plugin. Here, we will add the OracleFusion plugin in the input. This will enable the steps of Oracle component which will be added after this component to be executed with OracleFusion plugin. Click the "Click to edit" link over the keyword to input the plugin name.
6. Enter name of your Oracle plugin. Here we are entering OracleFusion. This name field is case sensitive and so you must enter the exact name of the plugin.
7. Now, let's go back to the test dashboard. Hover over the Automate section and click Test.
8. On the test dashboard, let's create a new test case where we will call our reusable components for integrated workflow. Click the +Test button and select Automated Test Case option to open the Create Test Case page. On this page, enter name of test case, select its priority and assign it to team member. Add a description and click Create.
9. Once your empty test case created, click the Add step button at the top. In the new step, search your ERP component and select it from the search results to add into the steps. We are adding the Salesforce component containing the SetGenericPlugin keyword in this step.
10. Similarly, add the Oracle component in by adding a new step after it. Click the add step button, search the component, and select to add it from the list.
11. Both the components of the workflow are now added to our test case. Click the Save button to save this test case.
12. Now, let's execute this test case. Click the Run button at the top. Select the Run on Browser option.
13. Next, select Local Run. On the Run Wizard window, select your agent and click Start Run. The execution will begin. (Make sure your agent is online by checking the green button in the agent dropdown)
14. Post execution, click the View Results button. Your test case should pass with the new step, and you will be able to view whether the test case is executed successfully. You can click on any step in your execution results to view its input and output data. For a failed step, check the Debug Info tab to understand the reason behind its failure.
You are at the end of this article. Click here to read the article on Load testing.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article