SAP Test Automation | SAP Automation with UiPath

uh so hello everyone so uh this is the uh fifth uh part in the sap test automation Series so so far we have covered success factor and fury

automation so moving forward to uh sa sap test automation what is sap and what is T automation so let's uh jump into

the next slide so hello my name is liby bandel and I'm a test automat developer at the Silicon partners and here is my uh LinkedIn

profile so you can uh reach out to me in case you have any doubt after the session or you can feel feel free to reach out to me if we can discuss

anything about uh test automation so meet my fellow speaker Shari thank you love hello everyone my name is Shar and I'm RPA developer in

the Silicon Partners feel free to reach me out in the link it will be pasted in the chat as well thank you U moving forward

so this is the agenda we are which we are going to cover in this webinar so the first one is what is uh sap and what is sap test automation looks like uh and

the second pointer will be test Automation and what are the components that uh involve in test automation third one is uh how we can automate with the

help of uip pass so this will be covering test automation with uip path after that what are the best practices that we have to ensure for a successful uh test Automation and fifth one is the

live demo so uh before jumping to the session I want to uh share that this will be going to a end to endend integration

webinar so you will be covering each of the expect what is uh sap what is test Automation and what what is the testing and what are the components that we

usually see in test Automation and then then how we can achieve with the help of you UI path test Automation and and follow by the live

demo so just uh going forward with the uh next slide so what is sap so as maybe some of

you will be aware of what is sap and please uh uh uh reach out in the comment if you have any idea about sap or do you

have have you any uh attended automated any test automation flow so far you can just write yes or no whatever so we will uh get to know that how many are aware

of these terms or is this uh new to uh everyone so uh so with the sap so sap is a enterprise resource planning software it

is wisely used by business enterprises the uh main goal of sap is to uh centralize the data so that each business user can

easily interact or share their data uh with very with ease and it will uh effectively reduce their time and uh and

also it will uh they can also assure uh overall efficiency with the help of that going forward to the what is SCP test

automation so we all know that uh so for sap test automation you must know what is test automation so in this uh that I'm going to explain in the uh further

slid so just give you a uh simple or short definition that you can automate any part of the sap uh maybe it is a application or a web browser thing or or

a module or a functionality whichever you want to automate so you can easily automate with the UI path or there are various other tool also available so you can use that that

also so moving forwards uh for the sap test automation the main uh thing is uh what is test automation maybe uh some of you are not aware of what is test Auto

automation so just let's get into our dive and uh let's understand what is test automation so moving further this

this is the test Automation and its component light so firstly to know test automation you should know what is testing why do we do testing so there are two types of testing generally we

have the first one is a manual testing and second one is automation testing and with the help of uip path give you a leverage that you can automate your test script with the help

of uh with the help of uipath uh test and and also can Avail in your systems so basically test testing is that that you suppose you have a functionality and

you want to verify it or validate it that for this that the suppose you have any product and you want to check it's working that it is working as per the

customer requirement or it is fulfilling the customer expectations or it is behaving as just like as it is documented in the earlier so for all

these steps we uh we are going to cover in the testing phase so so there you can see a cycle over here automated life

cycle testing so it has uh six steps so just go one by one and I will explain you uh very that you can easily understand that what

is testing and what are the all these steps that are in this so the first one is decision to automate testing so here we have to decide which module or which

functionality we want to automate suppose you have an create sales order and you want to automate that so in this particular step you have to taken into

consideration that I'm going to automate uh create sales order of sap going further that what is the test tool acquisation what tool you are using so

in in this case we I'm using uipath so the step two is done here and after that what are the testing introduction process so if you have selected any

module or a functionality so maybe this module have to we have to divide this functionality or module into different different sections maybe into different different task cases so we have to keep

uh this into consideration in the third step further on when each and everything is decided that we are going to automate this part and certain people are going to automate

this part so after that this will go jump into the fourth session uh fourth step so in this step we will going to develop all the test cases that that are

needed for this uh create sales order functionality so we will be we will plan design and develop all these test cases so when the development is completed we

will do testing at this end also and finally when the when the test cases are ready we will deploy them to the orchestrator or any other tool you have

so here they run and you can see the execution uh result so in the fifth step execution and management of test you are able to see the test execution what are

the test cases you have what are the uh ratio of the test cases pass passing or failing or you can uh can able to see a report and you can

generate that report also and uh yat also has a good feature that it it will downloaded a report so you can easily look into this and after that we will go

to the phys six point test program review and assessment so here we can uh uh group together and easily can uh um

with with the help of our team lead or anything we can uh see that what are the changes we have to done in our Tas cases that are failing and what are the major

or what are the best practices we can evolve so that we can uh going to further that the functionality is working properly or not so we can validate in this step so this is the

whole cycle of the test automation so going further so we can uh there are two uh different

platforms of sap that as sapg UI and sap Fury so basically sap Fury is a web browser based application that we can automate with the help of uh uh uipath

and sap GUI is a desktop based application that also we can automate with the help of uipath so many of the test cases many of the testing tools I have found that they have only

capability to they have only capability to they only have capability to test

only sap uh GUI but uhp GUI or a desktop based application but uh many of uh uipath is one of them it has both the

capability that it can uh easily automate ttop application versus web based application so in order to achieve this uh we must have testing in your

orchestrator Cloud so uh going forward I am uh going to uh give you a uh view that how you can enable testing in your

orchestrator if it is not enable so going further so uh so these These are the steps that we have uh to enable testing

in your uh orchestrator so you just have to click on the nine dots that is in the orchestrator so when you click on the these no. popup box will come and you

these no. popup box will come and you have to just click on admin when you click on admin button then you are able to see uh organization over there so you

just have to click on that organization after that click on on organization a page will be open so you have to uh

click licenses from here so just click on that licenses button so when you click on licenses button there are uh there are another screen will open up so

you have to just scroll down a little bit to that screen and you have to click on allocate license so when you click on allocate

license so you are able to see uh this type of a popup box and you have to provide the email ID and uh select a

license whether you can select both uh automation developer or tester both will work fine and both will enable your testing in my case I have selected tester

and so when you click on tester you can see easily see uh testing in your orchestrator and the one thing which we have to consider that the name which we

are going to provide in this uh text box it should be registered in this particular organization suppose my organization name is tspi so this user

must be uh this email ID that I'm going to enter in this name should be enabled in this so when you enter this you are

able to see testing uh in your uh orchestrator so let me give you a quick view how uh this will look like in the

real uh Cloud orchestrator so as you can see uh this is my orchestrator okay so uh let me share uh my

orchestrated with you so hope it it is visible to you okay so so as you can see there is the

orchestrator and there is there are so many tabs here so let me just uh the uh uh the

link let me just give you uh how you can enable the uh testing from the uh aast data so you just have to click on this nine dots after that you can see admin

over here so in the admin just click on the organization and click on the licenses part so you can see a window like this so you just have to scroll down a little

bit and you can see license allocation to users so here you can see and if as I told you in the describe you in the slides you just have

to click on allocate license just provide your name and give a automation developer or tester license and just click on a save so in this way testing

will be enabled in your uh orchestrator so when you when testing uh comes in your orchestrator so there

are the some components that you can see test set test case test execution schedule and test data que so we will go one by one what what so what are the

test cases test case is kind of a functionality uh that suppose we have a login page and it has username and a password and a register button so

suppose uh there are so many uh test cases can be formed with this scenario maybe uh user name is incorrect and password is correct and you try to log

into the system second scenar must be that both both inputs you are giving username or password are incorrect and you are trying to log to the system third may be user name is correct and

password is not in appropriate manner that it should be it is not alpha numeric and you trying to get into the system so these type of test cases a

similar type of functionality of uh test cases can be uh Bunch into or group into a single functionality just like uh

login will be the functionality here so so test set will be your login and each scenario you have is it is test case so test set is basically a group of test

cases that you are going to perform or that have same functionality and so you can see here that we have uh two or three test set

here and if I go here then you can able to see there are these are test cases here and after that if we I go to text

execution so you here you can see that when we try to run these test set or test cases what result we are getting so if you click on the three dots you are

able to see details and in this Cas this test case is uh fail so we can see uh the assertion or logs also ke what what is the reason why this T is failing and

we can also see the assertion that in which Step this this test case is failing so from here also from the loss we are also able to uh know that this is

the main reason that why this test Cas is failing so we can correct that and rerun that test particular test cases so this is the we cover in the test

execution after that test schedule so for test schedule we can uh click on the ADD test schedule button and so this is

the kind of a forms looks like and what is uh the test schedule why we use that suppose we have a deployment every Friday and we want to check whether our

test cases are running or failing before the deployment so suppose I uh schedule a test a test run or test schedule on the Thursday night so in the morning uh

Friday morning I I'm able to see what are the test cases are failing or passing I can correct that or maybe so this is the uh scheduling part so we can

uh schedule our test case accordingly and we will get the result so there is no manual intervention needed so it is will automatically handled by the arator

on the unended mode and last one is the test data queue what is the test data queue so if you are having any test uh

case so you you probably need data for that suppose if I have having a create sales order so I need what is the tile name what is the company code and other

amount or other anything we know it so we can just provide data in the form of CSV file and we can upload it here so whenever our test Cas is executing it

takes data from here and it will successfully run and you can also uh let me edit this one so you can able to

see that and the main thing is that uh it takes data in the Json format key value payers so you have to provide a particular Json format to enter data

here so this this is the test data Que so after that what the apart from the orchestrator we have test manager

so what we can do if test manager is not enabled in your system so in my case test manager you can easily view test manager here but in

some of the scenarios when test manager is not viewable here so the these are the steps so you just have to click on the

admin and after that you have to click on the default uh tenant whatever uh tenant you have in my case I have default tenant and you just have to click on that services and if you scroll

down a little bit you are able to see test manager here and in my case it is enabled so it is showing in a white background but if it is not enabled it

is showing in this gray background so you just have to click on this button and you have to enable it uh so when you enable uh this one you are able to see test

manager so let me uh give you a dive into test manager what is because test manager is the most important part of the uh sap test

Automation and uh whatever testing automation we have done in UI part the test manager is the main part so let me give you what are the components we have

in test manager and how it works so this is the interface place of test and manager so as you can see here are three test

project we already have suppose if you want to create your so you just have to click on this uh this create test set create new project and when you click on

this one button uh you have to enter a a meaningful uh project name and you have to provide freefix to that and after that you have to add description

whatever description you want to give so after providing gion uh just you have to click on create so you are able to

see your test project here so let's uh I will explain you my sap test sap test automation project so uh this is the dashboard

looks like so basically it has uh five to six uh tabs so the first one is dashboard in dash dashboard what we are uh the test cases

that we have in this particular project and what are the uh failure success rate of the test cases we are able to see so as you can see in the September 6th we have only one past test cases in

September 8 we have four past test cases and two fi so it's just give you you a overview so so by which you can understand that uh what is the uh condition of your test automation

project how many of them are failing or how many of them are passing after that click on the the second one is the require requirement so you can see here

are the requirement so you can specify your requirement as per your project and later down this requirement can be divided into test cases of your need so

uh we can divide so if you want to create a new requirement you just need to create click on this create requirement and you can create new

requirement and after that task cases so whatever task cases you want to link to that requirement you can create here uh there is a button that create test case

so you can create from here also after that test set so we will uh divide the test cases uh as per their functionality

and group them into a test set so whenever we execute a test set the whole two or three or five test cases whatever are linking to that particular test set run

automatically to execute them you just have to click on this three dots and click on execute executed automated so if if you click on execute automated it will start the

execution and after then when the execution completed you can see the test result so for the test result you have to click on this one a test

result uh and you are able to see the results here and you can also see the logs or assertion that we have seen in the orchestrator itself so the main

difference uh we uh in the orchestrator test manager orchester also give you Insight uh give you a execution log or assertion or but it did not provide you Insight but test manager provide you

Insight so if you want to uh view the report of your test uh test execution you have to select like

this or you can generate the Insight so let me uh give you uh the Insight that I have already created so this is the inside

report and when you click on this so it is uh it is the it is will give you a overview that how many test cases you

have and how many test cases are failing or top failing test cases are it will give you a GI and it will also give you

what are the common errors uh uh in uh failing test set and error pattern and also it also gives you a recommendation so by viewing this inside you can work

on your uh test cases and can change their functionality or the reason why which are failing so this is kind of a meaningful thing

because you do not have to go to each execution result one by one and I have to check for that you can view from here

also so after that clicking on this last tab that is a project settings so uh this this provide uh so from here you

can integrate your test manager with different Alm tools like Azure devops or or jira so just click you have to click on this integration part and you have to

just click on new connection and you can select uh you can see there are so many uh tools already are here so you can integrate in this demo we have

integrated with the jira so you can see that we can directly create a bug uh from the

jira uh for the test cases which is failing okay so let me just uh go back to the presentation uh is it visible okay

so the this is the test manager and its component so I have covered all the expects or all the components of its test manager and so if you have any

query till now so you can uh directly ask on the chat box we are uh happy to help and after

that test automation uh with UI path so this is the uh kind of a diagram so with the help of that we can easily

understand what we are going to demonstrate uh in this webinar so let me give you a uh

brief that how you can achieve integration or how the working of test manager and orchestrator works so firstly you have a test automation

project in your uipath studio so from here you create your test case and when you create your test case uh as we all know we work in if you are working in

any organization you need your code to be on the cloud so for that you need get get or any other tool whatever you want

to so in this picture we can see if I created my task case I can uh put push that data to the git and after that pushing that to git

we can also configure as Z devops pipeline um we are not demonstrating this in the this video but you can also uh uh use the cicd pipeline so whenever

your test cases pushes to the G that the pipeline got triggered and your C CD pipeline will integrate and it will perform so in this in our scenario when

we create a Tas case we will link that to the test manager uh whatever the test case is and whatever the test case we have created

in the test manager with the help of uip studio and uh linking and after that we will publish that so when we publish that particular test project it will go to the

orchestrator so what what we have to do here in the orchestrator we have to create a test set and we have to link that test set to the test manager because test manager can do not uip part

test manager for from now do not have a capability to run uh test cases so we need orchestrator for that so when you created your test set here orchestrator you have to link that to the test

manager and when the linking is done uh you can execute uh your test cases uh from the test manager it it is you can see the arrow is by directional so when

you initiate execution from your test manager the orchestrator Run uh your uh the module or functionality or test

cases is so so in this after that uip paath robots come into the picture because they are the one that running your test cases and whatever uh tool you

are using you are using sap Oracle or sales for what whatever you are using so they will uh automate your flow here and after that when the results complete it

will come back to the orchestrator and from the orchestrator it will come back to the uip test manager so you can view your execution result here and suppose I

have four or five test cases and one of them are is failing so what can I do from the in when I go to the result part

of the test manager I just click on that particular test Cas and and I create the defect from the test manager and it will

reflect to the jira so we are going to demonstrate this uh integration with jira part in our webinar also so this is

the whole process uh looks like how your test from the end to end how you created a test automation project in UI paath studio and later on you can create a bug

on jira so this is the end to end process so moving forward to the next slide so test automation with uip uh is

studio so uh so sha will be covering uh this part uh over to ISA thank you lovei let me share my screen real quick

I hope my screen is visible so test automation with uip studio so we are automating test automation using a particular template

that has been introduced by uip it is a test automation framework like any other framework it has all the exception handling logging and all the

capabilities that like any other template but this is specified to test automation which is also recommended in the best practices that test automation framework should be the one to be used

now moving ahead how we can get this template let me show it to you through Studio okay so first in studio we need

to go to home so in home itself you can see new from template and you'll be able to find it here in the template if you're not able to find it here you can

go to more templates and search it so that's how we can find this template so let's get back to the slide so once we

download this template all we need to do is so what this test framework consists of like any template it has a separate different structure it comprises of

setup test case placeholder and tear down so setup as a name itself suggests setup is uh basically recommended to use

to get the data be it from assets or to prepare the test data if we are reading it through the Excel and uh it reads the configuration file and if we are doing a

web automation we can you know login or load our browsers and if we are doing any application automation then we can simply log into that application this is

what setup comprises of and the test case placeholder is the second part in which basically there is a execution timeout activity in which a placeholder

is placed so this is something that comes at the time of execution so we are not supposed to invoke our test cases within the placeholder or anything if we use this execution

template within the test case so while the execution it will automatically invoke the test Case by itself this is something that we'll see further while

we run the demo okay so moving ahead we have tear down so tear down part is basically responsible for closing the browsers logging of the applications

preparing the reports like in our case we are fetching all the screenshots from the sap and preparing a Word document out of it and attaching it to the test

case itself so this is what tear down is responsible for let's go to the studio and have a look how the test framework actually looks like so this is our test

framework this is the setup part it also mentions everything in The annotation itself so moving ahead this is what

the test case placeholder looks like so it comes within the core activities it doesn't need to be downloaded and this is some this is one of the activities that can only be used in the execution

template itself so moving ahead this is the tiar down all right let's get back to the

slide so before we jump on to the live demo let's go through the best practices so test automation framework is definitely one of the implemented stable and scalable

automation template uh which is recommended by uod to be used in case of testing and they also recommend that each task case should be independent one

should not be dependent on the other one also suggesting that each Tas case should be able to handle their own exceptions right and moving on so each task case flow should contain only one

verification of course these are the things that can be tailored as per the requirement but but this is something what is you know suggested by the uip

path itself so moving ahead a test case template basically comprises of sequence given then and then so whenever we create a new test case these are empty

sequences which are suggested given is responsible to loading your very first screen in which we have to do the automation from where we have to take the for automation for further and then

has the basic core steps of the functionality and then is responsible to hold the verification part specifically so in case any of these sequence is

getting too extensive or it's a bit complicated and unmanageable in that case it is recommended that we move to a much smarter way of automating it for

example in our case we had a you know number of steps that were automated within the sap GUI so what we did was we completed that part in the workflow and

simply invoked that workflow within the part so that's how it is suggested to do and also it is also recommended to use

cicd pipeline also the selectors that we are using should be in the object repository and libraries are suggested to be used the library is a couple of

like chunk of the test case or the steps of the test case that are particularly being used again and again can be automated within the library so for example login part if there are three developers working on the same project

and they have to deal with the same application so login is something that would be same in all their parts right so this can be created in the library itself and it can be invoked at any

given time right and the selectors are suggested to be an object repository so object repository basically saves the selector in a way that it is accessible

throughout the project itself they can also be imported or exported to different projects if required so if I need to make any change within the selector I can make that change in one activity and if it is added in the

object repository it will be refle reflected within all everywhere where that activi is being used throughout the

workflow so moving on so these are also not specific to test automation but also spec U for the entire automation these

best best practices are recommended so we need to have retri Scopes we need to do the exception handling and logging in the right way so that we can you know be

able to track the bot and understand where the exception is coming also track the progress itself and the activity names are suggested to be in a way where

uh you can Define the action of that particular activity in case you're not able to name it in a way we have annotations to explain the process further right this is something we have

already you know implemented in our code and I'll also show that to you moving ahead we are not supposed to use hardcoded delays which it is not a recommended way how we can avoid using

hardcoded delays is something also we have added within our code and moving ahead all the type PS and clicks are supposed to be simulate type and in case

simulate is not working for any activity we can also use Windows message so also the test case we should not remove or delete any test case but there is also

uh an option where we can import the test case from any other project so this is something which is recommended with the best practice moving ahead let's go

to live demo let me go to the studio all right so we have seen how we can download this template let me show you what this template comes with so these are all the activities um all the

packages that were already the part of the template I need not to I didn't have to download any of this separately and also the data folder it

consists of a j file that is specifically recommended to be used for Ence so we do not have a config file in this one and we are specifically you

moving forward you'll see we are not using a config file in fact we are using Json and also we are using constants in the data manager part to maintain our constants variable and we are

maintaining and getting assets using this Json fire so we have automated basically two of the test cases one is create sales order and the other one is create outbound

delivery so these are both part of order to Cache process in sales and distribution module of sap so this is how the first test case

looks like it has the given then and the then sequence as explained earlier so the given one

basically it gets data from the cube and it calls in the transaction v01 so this is it will take us to that particular page and whatever function we need to perform are mentioned here within the wi

so I have invoked the workflow that comprises of all the steps that are needed to be perform in particularly create sales

order and in the then part I have this verification so this verification there are different type of

verification that can be used I'm using verify expression with operator I can also so we have these are all the options that are available we can use

verify control attribute verify expression and verify in range so control attribute allows you to invoke any one of the activity and use it to

compare to get your exact result you can drop the activity let's say I want to drop get text and I want to figure out if the text that has been taken from the

screen is equal to some message for example if I use it right now I can used to take it anything like live demo from the PPT itself right and I can

compare it here if it is containing of that particular text and its result can be stored in the result output so this

is one of the verify activities when we have is verify expression it's a simple activity where you can write in your expression or simply pass a Boolean

result to get your output and verify expression with operator some we are using and this you can use a comparison box in which you'll have your first expression the one you want to use it

compare use it to compare with you can use the operator it can have equality inequality if it is integer type value which you want to you know compare and

minus string so I'm checking if it contains a specific term which is saved then only it will be considered as past so all the uh activities are different

but the only thing that is similar is the properties part so it will have a alternative verification tile so alternative verification tile and output

message format or something that will be uh that will be reflected within the test manager itself and also in the uh orchestrator so whatever message we put in will be visible there as well and

I'll show you how this can be done output message format can be specifically used to follow a same approach throughout your test airation project uh this is something uh that can

be followed in all of the test cases so we'll go ahead and have a look at how it looks like in the orchestrate as well let me run

this automation first so the very first one I'm running is create sales order also I have added in break points in between so that I can you know

explain it while it runs so it will go into in it all seted uh assets and it will read the Json file and then DC realize it and then check if

any of the Json asset values are empty if not it will assign it back to the dictionary and that dictionary variable uh argument is being passed throughout

the workflow so right now it has fed the sap credentials and all the asset values connection and everything it has logged in successfully now it will put in the transaction which is specifically for

create sales order now here on the screen it will put in the order type and move

further it clicked on enter for better understanding highlighting element has also being turned on so we'll put in

sold to party data and then customer reference customer reference date all follow by the line item

values material and Order quantity yeah so it will check for sales area it will select the sales organization in

this case it's 1710 we'll hit enter and moving ahead it will go into the material

itself update the audit quantity and then it will check for schedule lines it will fetch the delivery date from here which will be used

further now it will go into the condition Tab and update the amount so as you can see the amount has been updated once it's saved it will create our sales

order so the sales order has now been generated so at the end once it's able to perform all these steps it

will create the word document file and also it will upload the same all

right so it came down to tear down part so I have added a breakpoint because I wanted to show what all things we have added in the tiar down let's go ahead so

it consists of create final document sequence where and we are fetching each of the screenshot that we say in the screenshots folder this

is this is the screenshot folder it will fetch in all the screenshots and then make a Word document Consolidated one and then upload it finally to the test case since we are running it through the

studio this activity won't be working but uh it is basically designed in a way when the B runs in unattended mode it will automatically fetch the report and

upload it in the test automation itself so let's continue as you can see we have the test case has

passed successfully and it also showing the order number and along with the test data que item that have been added

okay so it will also add the end we are deleting the screenshot folder and the output folder itself so before we delete it let's go ahead into the project folder and see how it looks

like these are all the screenshots uh that were captured during the automation we are creating this folder and U deleting it at the end every time

so let's go to the document that it just prepared it will be in the output folder this is how the output file looks

like so it will not only append the images but also take the name of the file and paste the name so it's much more clear that way so it has entered

the data successfully first the delivery date entered in the material values and sold to party value now the same document would be uploaded in the test cases

itself from this end to end all right this was create sales order let's go ahead and run the same for create outbound delivery it will also F the

details and then we'll go to test manager and have a look how the execution actually looks like so once the execution is complete I also would like to show you what a

generated test case File looks like and what it does let me show it to you now okay so this is something uh which is

only created at the time of execution so generated create sales order was uh generated at the time we were testing this particular test case so as you can

see it is exactly same as the test framework that we were using the only difference is the test case framework had a test case placeholder but this

generated file has the test case invoked itself so we do not need to invoke it all we need to do is while creating uh the test case we need to write cck and

Set uh the execution template once we select the execution template we'll be able to see exactly this framework

working in this way also we do not need to map in the assets if we uh create the if we create the arguments with the same name that are present in the framework

it will fetch in the data automatically as soon as it is invoked so I did not invoke my workflow anywhere the test case but I only created an argument with the name of assets and there was this

one variable available within the framework with the name assets so it mapped it automatically at the time of execution so let's continue this

automation going ahead right it's reading all the assets okay and it will kill the sap in the background if it is running and then

it will log in back again so it will put in the details which are required in this case it is shipping point it will update the date it's fetching all the data from the

quebe and it will upload the sales order that was just created and then it will hit enter and click on

Save also it will update the pigged quantity Y and now the create outbound delivery has been completed so it has created a delivery as

well okay so in this case we have used simply verify expression and have put in the condition wherein we are checking if the FED message is empty or not so since

it was not empty and it had this message it simply approved to be as true and I'll go ahead and continue this

one okay so it has the same tiar down process we already went to went through this okay so it will delete the screenshot folder and delete the output

folder at the end all right so once once we download the test automation template and design the test cases as per our requirement what we need to do is we need to set up

a connection to the test manager itself for that we need to go to test manager setting and put in the link of the test manager and hit on connect so mine is connected right now and also the

individual test case need to be linked to the test case in the orchestrate to so it has a separate link since this one is already connected it's asking you to

link or unlink let me show it from here here so for example this is one sample that I have kept we can click on set execution template and select the template that we desire this is test

automation framework then we can simply mark it as publishable and if you want to link it to the test manager we can also go from here link it to the trust manager it

will give you the option so the project that love you already demonstrated was available on the cloud this is the name of the project it will fetch in the det

also you can put in the name of the test case or the ID so we I can link it to all of these test cases that are already available there in the cloud now let's

go to the cloud so this is how the orchestrator looks like I have first published the test cases from here and then I created the test Cas test set

within the orchestrator I can select this one or more than one and then hit on ed test set it will ask me the name and simply will let me create the test

set right then what we did is we went to test manager and simply linked the those test cases here it will fetch in all the details from the orchestrator

itself so this is how we created it let me show you the results when we ran so in order to show different results we ran the couple of test cases in

successful manner also won with the failed result because we also wanted to cover the defects part so the output file that I just demonstrated would be attached within here in the test

execution let's see what all test result con contains so the verification activity also captures the screenshot this verification activity had this property if you want to take

screenshot of the activity failed or passed so I logged it on through for both of these so this is what happened so it captured the screenshot the final

screenshot where the standard order was created this is the verification TI name reflecting in the assertion itself and this is the output message format coming here so we can set this across a test

automation project so these are the execution logs these are the same logs that are also visible in the orchestrator also moving ahead execution

details will have the name of the framework you are using and your machine details so this is the same output file that has been uploaded and we can

download it and view it from here so let's go to a failed result all right so in this case it will also

capture the screenshot in this case it will also capture the screenshot in case it is failing because I have turned that uh property setting on right so it

capture test exception has been occurred and Q item was empty this was the reason of the failure right it will show the logs and also the attachment for the

same right also once a test case fails we get this option to create a defect this one is already this project is already connected to a

j as already mentioned before so if I'll go into the test case results I can simply create a defect for the same it will give me option to create a defect since I've already created a

defect it's asking me to unlink the defect what I can simply do is we can also go to its results and view

the link itself this is TA defect if I click here it will automatically take me to the jira session where this defect was uploaded so it will fetch in the name of

the test case and with its result it failed and also fetch in the logs for the same so this this is how it works

overall and that's all we had for the demo moving ahead for the slide do we have any questions

I think the queries have been answered in the chat itself thank you m so if we have any further questions please feel

free to ask or put it in the chat Maybe if not then maybe we are good uh thank you everyone that's all we had for today so

these were the resources that we used for this for this demo and moving ahead so we have further more

sessions so um I guess we just got couple of questions around uh the session so the first one is can you explain any difference

between cloud and on Prim test manager uh so we have not used the on PR test manager as of now but uh definitely uh this is since this is also available for

on premise version uh which is a part of test Suite so um I guess uh you can follow the documentation which is available on Art uh docs there you might

find some differences if if any right so the next question that we have is uh in this session you will

cover the establishing connection to sap to show sap heat map right so uh so this uh this session will uh happen I guess

maybe somewhere around in October where we will show you how to establish a connection with your SC instance with test manager uh a test manager project

and how the Heat Map works so uh you will seen uh soon see a session posted on the event page under Delan

here and yes as recording uh this sessions link will be shared uh it will be available on the same L same page where you registered for this event and

uh you can have a look at it maybe in a day or two it will be available all right and uh feel free to register for the upcoming sessions so the next

session that we have is on uh the solution accelerators for SCP uh so this this session is uh scheduled to happen

tomorrow uh feel free to register yourself uh for this uh session and uh I'm just pasting the link to the next

session on the group chat feel free to register if you have not already registered for the session uh and then we also have a in-person Meetup

schedule to happen on 21st of September uh which is on Saturday uh feel free to register yourself if you are in uh Delhi

NCR region so this on uh inperson Meetup is uh will be happening at the sleeping Partners office in NADA location uh you can register yourself

uh on the same events page uh I'll also share the the link to directly access all the sessions uh around sap

Automation and this also includes the link to in person all right thank you so much everyone for joining the session once

again and feel free to join and the dedicated uh we Alan and Meetup WhatsApp group where we discuss about the upcoming events and uh any discussion

around uip paath and the inperson meetups um I hope you're liking this series and uh we'll have two more

webinars coming up and one uh iners meet up at the last of the session where we will be providing exclusive uh temporary access to do some handson

exercises uh during inperson Meetup thank you thank you thank you thank you for