[AUDIO LOGO]
AJAY JAGTAP: Hey, guys.
This is Ajay Jagtap from UiPath.
And in this video, we are going to demo
an end-to-end an interoperability test
automation.
Usually, an end-to-end cross application test automation
is difficult, time consuming, and would
require different toolsets for different applications need.
With UiPath test suite, we can build and manage
the test from one place using intuitive logic
across the workflow.
We can simply design the test in minutes,
and it can run repeatedly where the values set
in one application can automatically
be used as a direct input in the downstream applications.
Benefit of an end-to-end cross application test
is it tests the way multiple users work across applications,
removing the extensive handover among different users.
So for this cross application test scenario,
we are going to run through four different applications or Uis.
We will start with Salesforce Classic
for creating an opportunity using an auto generated
synthetic test data.
Then we will move to the complex SAP Fiori web application
to create a simple sales order.
Use that order number to create delivery and billing
documents in SAP GUI.
And finally, we will conclude our test
by creating a data file in AS400 through a green screen
emulator.
And during the end to end execution,
it will also run through some verification steps
that we will check out.
All right, so let's jump to the UiPath Test Manager
and execute the automated test break.
Now, I have configured my robot to execute
on my desktop for the unattended automation,
so it will start the execution in my desktop
with the Salesforce Classic application.
So it will do the login process and start the opportunity
creation process.
And as I mentioned earlier, it will
use an auto generated synthetic test data
for creating the opportunity.
You can also retrieve the test data from various data sources
like Ms Excel, Flight Files, SQL database, or in fact,
any database that we can connect through
and what we see are API connection.
Once it creates the opportunity, it verifies the status
if it's closed one, and then logs out from the system.
Moving on to the next application once it logs out.
So now, it is going to open up the SAP Fiori application
and it will log into the system and start
to create the seals order.
So it's going to enter the necessary data
like order type, sales area.
And then, it will enter the other information
like sold-to and ship-to party.
And also, the customer reference,
it is going to use the same opportunity name
that we created in Salesforce.
It will then enter the item level info
and complete the creation process.
Bills order number that SAP generates
will be parsed and used for the next application, which
in this case is going to be SAP GUI application.
So here, we are going to log into the SAP GUI,
use the order number that we just created, and it's quickly
going to create a delivery and also the billing document.
Log out from the system.
And lastly, it will move on to create a data file in AS400
to a green screen emulator.
Once the test is complete, we will get the results back
into the Test Manager.
So let's navigate back to the UiPath Test Manager
for reviewing the test results.
So here it says, the overall test has failed.
So let's check that out.
So this is the latest one that we just executed.
We just go ahead and open this.
So when the test, we had five assertions or five verification
steps.
The first three passed, where the first one
it successfully verified the opportunity
status to be closed one.
The second and the third steps also
passed where it successfully created
the sales order and the delivery documents respectively.
Two however, failed where it tried creating a billing
document but failed due to the incorrect processing status.
And then it tried to create a data file with the name which
already exists in the system.
All right, drop down the steps.
We can also check the screen capture taken
when the failure happened.
Now, if I have connected an ELM tool
like JIRA, or Azure DevOps, or any other area that is there
in the system, connect to my test manager
and easily create a defect for the field test case
from the Test Manager itself.
So as I hit Refresh, you will see
the defect number is being auto generated
from the JIRA in this case.
With that, we will conclude this demo video
for the end-to-end interoperability test
automation.
Thanks for joining.
Have a wonderful day.
[AUDIO LOGO]