UFT 12.01 | QTP | Using Solution Files Video Lecture | Automation Training with HPE Unified Functional Testing 12.0 - Software Testing

hello everyone welcome to the video
series on eft automation in this video
we will look at solutions in particular
how you know naming solution files the
test cases and actions now we did look
at you know renaming actions and adding
multiple actions in other videos but
this video will focus more specifically
on the solutions action names and test
cases what I have here on the screen is
a solution which is untitled and I have
a GUI test with the name test seven and
an action which is actually one it's
primarily a blank test ok what I will do
is I will start customizing it to my
needs first you know I'm gonna rename
the action to log in because I know that
I'm going to use this for flight
reservation application say login and I
want to rename this as well I'll do save
as and to begin with I'll say want to
start with 0 0 and C initial test so has
a meaningful name there and for solution
I'll save the solution file as this say
flight reservation this test set 0 1 so
I have a proper name for solution for
the test and for the action as well now
let me go ahead and add another action
to this test and this would be exit so
login and exit that's the whole point
here along this how I want to do it
and for the login or I'll do is I need
to start the application I'll use a
system you know dot run to start the
application here I'll do record run
settings I need the path for the
application so that's the step to start
the application so to make it a little
more interesting I'll add another action
we'll call it in it and it is used for
starting initialization so from logging
I'll take this out put it in
initialization action in the login this
would be blank for now so let me go
ahead and start the flight reservation
application and keep it ready for
recording I'll go ahead and record real
quick I want to record within the log in
action as here record and we'll say test
so the login is done now I want to
record this in know the next days I
don't want to book any flight but I want
to exit the application but I want to
record that in a different script
different action go ahead and select
exit so now it's switched to exit now
I'll do a file exit so the exit got
recorder here closed so that this step
is just you know I was moving the screen
around so it kind of captured it all
deleted so this this interaction has a
step to start the application login to
login into the application exit it will
close the application let's look at the
canvas login exit initialization so we
need to move this up and for the more so
initialization login makes it so now we
have these three actions the first
script and have a proper structure here
so I have some meaningful names for you
know all these you know different
entities within our solution Explorer
now I'll go ahead and add another new
test case for this and I'll call it zero
one underscore book single ticket so
that now that that has case it's added
to the same solution so have 0 1 0 sorry
0 0 and 0 1 and here let's say now I
want to book a flight but I already have
initialization login and exit all I need
to do is a book of light here so let's
say I'm gonna rename to begin with I'll
rename this action to Burke single
ticket
and now let me have the application
ready for recording test we're curing
have it now I will go here make sure my
book single flight is running or you
know active that's what I meant
else our recording so just move things
around so it's easy to observe things so
it's recording so add the date pick two
different cities so to the flight okay
name they're two tickets and so record
that's fine there was an error that's
okay with me
sir one more time
okay there's little issue with the
database let me see you this is my scene
with I think that thing okay that's fine
now we have an error there but our focus
series on the solution files I'll go
ahead and stop recording so have this
see so insert here so here's all the
remedies sorry you know I have this
recording with there or that's fine so
if I were to run this test you to fail
because if you look here let me close
all documents here and let me so it is
starting I mean it's looking for flight
reservation if it is run this chest and
it will fail if you go to the canvas you
can see you know start and book of light
if I run this chest it'll fail because
it cannot find a lot you know it will
not be able be able to find the
application unfortunately hide it open
I'm sorry let me go ahead and close it
that was not my intention
let me close the application and results
this is not required because it's the
same insert thing let me go ahead and
run again it'll fit the very first step
because it's looking for flight
reservation screen and there's no such
screen we haven't started the
application yet so now what we can do is
we can take advantage of the actions
from the other script that we have
because by default these actions are
reusable actions if you go to the
properties of action you know it is a
reusable so what I can do is I can
instead of you know me adding you know
are creating new actions here or I can
you know total new actions and having
those scripts steps to start application
to close and all that I can add call to
existing action so I can use our other
script and from here I can borrow these
I can say I'll call in it and then I'll
call or start using exit then you know
do another thing called the existing
I'll call the login so I'll call all
three that I need and I'll go to the
canvas
I'll start adjusting things here I want
to of course first initialize where is
initialize login exit book of light so
initialize got added in here it's inside
this so it all depends on the way you
add it let me delete that this I'll go
ahead and add one more time
right click here add existing action at
the end of the test zero zero and I need
initialization our unit action from
there go to the canvas again so here
we're gonna initially we know that in
its action will you know start the
applications of all one that to be at
the very top so in its then after
initialization we need to log in so we
will move this up then we can book a
flight and exit but all I had here is
book single ticket so let me go and run
this now it'll probably have the same
error that's fine in this video I'm
trying to you know demonstrate the
purpose of naming or solution files in
test cases and actions you know more
appropriate to the business so now look
at the solution file now I have two test
cases in this solution file with with
very good names very professional and I
have in a proper actions will go ahead
and save everything is here I'll just
close the solution now let me go and
open the solution again I'll say open
solution this time not chest but
solution and this thing is in our temp
location temp 1 and here it is for test
set 0 1 so when I open the solution all
the tests tests that we added within
solution gets loaded so this out you
started multiple tests within one
solution and you can add up to 10 tests
here type you 1010 the good thing with
this is that you know you have access to
this script right within the same
solution you can look at any scripts
that you like or any action that you
have and the good thing is you know you
can you know you can import I mean to
say you can call the existing look at
the code there make changes if needed
here and then you know it's already you
know
being used here you make a change your
save it you know you can run this script
so anyway that's all about solutions and
you know you can depending on your
project you can you know make best use
of the solution and having multiple
tests within the same solution well
that's it and please not hesitate to you
know rewind and watch the video again to
get a better understanding see you in
the next video
thank you for watching this video
thank you