UFT 12.01 | QTP | Transactions - Win Flight Video Lecture | Automation Training with HPE Unified Functional Testing 12.0 - Software Testing

hello everyone welcome to the video
series on UFT animation in this video we
will look at transactions okay a
transaction you know in general you know
a transaction is something that has a
start and a finish so when you when you
start something and finish whatever
intended activity associated with it
then you say the transaction is done say
you're trying to transfer money from an
account another account in banking you
know once you transfer the money from
your checking to savings and I cannot
get debited the other con gets credited
and then the transaction is set to be
done so in our EFT software here when
you say transaction you are trying to or
that is a way to determine how long it
takes for your certain activity to
complete meaning you will insert
transactions anywhere you like primarily
you know depending on your business
functionality right say for example you
want to determine how long it takes for
you to login then all you have to do is
you have to start a transaction and end
transaction I mean to say this you have
to end the same transaction at
appropriate points within your script to
determine how long it takes for the
script to finish that portion of the
script say for example I have our
standard sample flight to the vision
application and you know it's a pretty
standard script that we have seen the
other videos it has a login action it
makes the reservation and it will close
the application let's say I want to you
know our goal here and let me look at
talk about this you know we have a goal
here in this we have two goals first is
200 remind how long it takes for the
login action to complete you know
because it's gonna start and then
complete so we want to know how long it
takes and then we want to determine how
long it takes for the application to
display the reservation screen after you
click the
okay button on the login screen so those
two are our goals so let's start with
one the first one so first is we need to
determine how long it takes for the
login action to run so we are already in
the login action and you know all these
are Commons that means it starts at line
15 so you want to know how long it takes
for the script to run from line 15 to
line 27 that means we need to start
something here or we need to start some
sort of timer so I'll say start timer
and we need to stop timer so if you if
you were to literally use a stopwatch
and kind of start it here and end it
here then that pretty much tells you how
long it took to finish this particular
action so equivalent to that is adding a
transaction and this is how you do it
design start transaction and you will
say login action I can give more
meaningful name to a name depending on
your kind of business you do and I mean
to say the kind of application you're
working with and kind of thing that
you're doing so I'll just say login
action I'm just trying to demonstrate
the functionality here so services or
just our transaction and give the name
and here I want to end it I can do a
couple of ways I can do services dot
again
yeah well this TLC in transaction I'll
give the name login action this is work
just fine
I'll go ahead and comment this out and
I'll show you a different way into the
same thing design end transaction so
that's the transaction we started
there's all let me take this out
and let me know I already have this
transaction so take that out let me make
sure okay
let me save the script so as you saw you
know you could actually you know enter
services or in transaction give the same
name here that means it's starting here
ending the transaction or you could do
design in transaction you'll see the
transaction that was started within this
action you can pick that one too okay
it does the same thing it adds it so now
the transaction is done let me run the
script and see what kind of impact this
has on our reports or you know results
okay here are results let's go take a
look at the transaction so that's when
the transaction started and let's go to
the end transaction and at the end
transaction it tells duration is one
point one four seconds so that's the
duration that's the time it took for the
script to finish the action I mean the
login action so that was our first goal
now let's see how long it takes to for
the application to display the login
screen nor the long stream of the
reservation screen after you click OK on
the login screen so this is where we
just clicked ok because since we know it
is an automation script and it does the
first thing and it immediately clicks
the login button let's let us time it
right before it clicks the ok button so
we want to add a transaction here we'll
do design start and this would be user
authentication time because you're
clicking and then you're logging in I'll
just name it I mean of course you know
you can give it a meaningful name
depending on the application you're
testing but I'll just stick with this
one user authentication time click OK
so it just added you know a similar line
services dot start transaction in it
could this could be any name and we had
a login action here so we want to start
here and then go in to make reservation
and then add here because this will
after a line 7 it is safe to assume that
we have the flight reservation screen
open on the screen I mean to say you
know on the on your monitor so now let
us end the transaction here and you
might have a challenge let's say and you
might think that look let me go here and
in but you may not see it so what you
can do for that is just enter the thing
services dot in transaction
and you need to give the name and the
name is very simple go to login grab the
name from here and paste it here did
that now you just started a transaction
a second transaction here and you're
ending it in the other action so it can
overlap let's go ahead and run the
script and see if it really runs or if
it fails because we have it start in one
action we had nd another action looks
like it went through just fine let's
wait for the system to finish and we'll
look at the report I mean to say the
results it looks like it ran with no
errors start transaction there that's
for the login action so we started user
authentication here at this time we
ended login action within the login
action I mean the transaction it took
1.2 seconds we started the user
authentication time transaction within
the login action but we ended it in
flight reservation screen our flight
sort of make reservation action so this
is where we ended it so it's tell the
duration is 2.5 4 seconds so that means
that's the time it took for the you know
from the point when you add up this
transaction so right before you clicked
ok you started the counter and you
finished after you you know saw that you
know after the first step there which is
you know it was looking I believe you
were moving the screen little bit or
clicking there some some sort of
activity there so so that you know this
second transaction that we added gives
you the time it takes the user to add
for the screen to login and display you
the flight reservation ok let me close
this results here so let's now let's add
a third goal our sales so we want to
know how long for the how long the
script takes to run completely I mean
because this is
rate run you you know it's just I'm
under climate ticks but when you have
more checkpoints when you have you know
a lot of data to process meaning when
you have any parameterize your test and
then add a lot of transactions a lot of
bookings that you want to make through
the data driven script and if you want
to know how long it takes for the
checkpoints and how long it takes for
the data to process so you can check all
that but you have to add the
transactions at the right spot because
you know you know you know start to end
right and depending on what's between
start and end you know there's a meaning
to it so let's say for example I want to
you know determine the whole time you
know from start to finish your to know
how long it takes that means I will add
a transaction here sorry design start
transactions I'll just say start okay
start script I'll just copy that go all
the way to the end which would be exit
and this is when where I end and I know
this is now start transaction this is
end done so if you run the script now
that put the transaction because it's
starting that's a very first step and
then it's ending it's after all the
activity so that transaction will tell
me how long it took for the script to
run all the actions if I were to
directly go there I can just go here
start transaction that's where you're
ending in transaction that's a
transaction we're dealing with it took
eleven point eight nine seconds to log
in book one reservation and exit but now
you know if you add let's say if you
want to make twenty reservations right
this time will increase so and you'll
get an idea what kind of impact you know
the check points
and what kind of impact the dairy is
having and not just that sometimes you
know the script might run slow that
doesn't mean that the script is running
slow it could be that the system is not
responding to you let's say you're
trying to book a flight you clicked ok
you know insert booking or in that
insert button on the screen but if the
system is not responding meaning the
database is not responding it might take
you know maybe three four minutes right
there now you know it might get lost and
get an error so things like that will
happen and you know if you add
transactions at appropriate location it
kind of gives you an idea if certain
areas of application or slower than the
other depending on what you do again it
is it all depends on your business
knowledge your you know your application
knowledge and your familiarity with the
environment sometimes you know your
terabits might be slow and it might be
you know slow for a long time in for
months and months and it might be
something else with that thing and there
could be some database issue there could
be a disc issue on the database system
but this will kind of give you an idea
so primarily a transactions are
something where you know you add a start
an end and you will know how long it you
know it takes for a script to for that
portion of the script to run so anyway
that's that's about transactions you
know feel free to rewind and watch
because you know you know probably when
you watched for the first time you might
not get a hang of it but you know watch
a couple of times it's a very easy
concept but it's very powerful I mean
the concept is easy but it's quite
powerful because it gives you that
amount of information that you could
actually quality of information that you
could take and talk to the team because
you know it tells you how long it takes
right that's a powerful information
especially in meetings okay well I hope
you enjoyed this video I will talk to
you you know the next video
you
you
thank you for watching
thank you