Hi Saket,
We use a Driver Scripts to call all our Test Cases.
And it is not only at the end of each test we use the KILLDLL but we also use it at other places to exit from the application.....
Ex: Lets assume we are logging into the Application... and incorrect credentials are entered then system veries userid and then handles the screen.
Below AppKill = Yes.. set the Flag.
Mentioned above was just an of our scenarios where DLL was used to handle the odds. Then test case fails and the driver scripts pushs the code to start with the next Test Scripts as mentioned in the driver file - Data Sheet.
So in a similiar way.. where ever necessary we have used this DLL to close the applciation.
Hope this helped. Please let me know if you need more information w.r.t the same.
Kill_Application is the Scripts that calls the DLL and then the DLL does the necessary.
We use a Driver Scripts to call all our Test Cases.
And it is not only at the end of each test we use the KILLDLL but we also use it at other places to exit from the application.....
Ex: Lets assume we are logging into the Application... and incorrect credentials are entered then system veries userid and then handles the screen.
Below AppKill = Yes.. set the Flag.
Code:
#Login would happen only if the current user id is different from the previous userid - [i]Comments[/i]
if (( ( userid != previousUserId ) && ( userid != "" )) || (AppKill = "Yes"))
{
#logout the application and Re-Login - [i]Comments[/i]
if(win_exists("garwin",3) == E_OK)
{
call "\\..\\lib\\Kill_Application"();
}Mentioned above was just an of our scenarios where DLL was used to handle the odds. Then test case fails and the driver scripts pushs the code to start with the next Test Scripts as mentioned in the driver file - Data Sheet.
So in a similiar way.. where ever necessary we have used this DLL to close the applciation.
Hope this helped. Please let me know if you need more information w.r.t the same.
Kill_Application is the Scripts that calls the DLL and then the DLL does the necessary.
