UFT | QTP | Database Checkpoints - Part 1 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
database checkpoints so and I'm gonna
use a blank script and not doing
recording directly add a database
checkpoint and run it so the script will
directly connect to the database and you
know do the kind of checks it is
supposed to do based on the SQL
statements that we add
so before I start adding the database
checkpoint let me assure you the
database environment that I have so what
I have is sequel server 2002 or Express
edition install on my local machine and
you can see it's SQL Express it's 2012
then I have sample databases I'm going
to work with adventureworks LT 2012 and
I have a sequel statement here and all
I'm doing here is I am counting the
records from customer table where the
last name starts with the ve and I have
8 and if I do you know all the names
that start with we have 34 so let's keep
it this way 34 so we'll use this script
and database server itself is the
computer name slash SQL Express that
would be your database server and the
database name would be adventureworks
you know LT 2012 so we only use these
three pieces of information to connect
to the database and run this script so
let's go back to UFT and do a design
checkpoint database checkpoint and i'm
going to do pick the second area button
and specify SQL statement manually click
Next
for the connection string
I can create and pick the one I already
created but let me show you the whole
process I'll do new and pick sequel SQL
Server from here click advanced and here
I need to you know give the server name
and database name as you can see the
syntax is server equal to server and
database equal to my database so it is
server equal to I need let me go back to
the management studio
I need the server name and that's the
name this is nothing but what you have
here so primarily I just need to name
the system name a slash and the SQL
instance when you install SQL Express
Edition that this would be the default
instance name but if you have a sequel
server standard edition or Enterprise
Edition you know and if it is a standard
instance meaning it if it is not a named
instance then it should be it will be
something like that there would be no
such thing called slash in something but
in your test environment you know on
your machine you can when you install
SQL Express Edition then you end up with
this but you know in your in real time
you know you know you can ask your IT
administrator or who or maintains your
test gear they can give you this piece
of information maybe it could be
something like some system name slash
you know QA database something like that
and then we need the database to you
know for it to work with and the
database name is adventureworks LT 2012
just go ahead and copy from here I'll
try to copy text as much as possible so
if there are any typos you know I can
just pretty much get rid of all that
because I'm just copying and pasting
I'll do okay here it's done do next and
it says you know I can see whatever I
you know the database name the server
name all that can be saved and just say
new - that's a you know DSN name so
that's a period that's information that
it's saving the it's a data source
that's we're saying that as DSN that's a
file name if you open that in a notepad
all you'll see is all this you know the
the driver and then you know the server
and the database name so this
information will be in the file click
finish and query new database source oh
I think I stepped on it don't need to do
all that select a database source I need
to go back to D sample data
oops I'm not sure where I saved it let
me cancel all that I would start from
scratch again okay on the screen click
create and we'll do new and SQL Server
I'm sorry into advanced then the server
equal to database equal to that's the
database name and the server name let me
get it from the management studio
that's a server or a work with so that's
the name or a cop copying this one put
it in there okay next add the name of
the file those you want to save this
connection to I want to save it to
this location good to save so the name
is there the whole file click Next
finish so I have it I'll select the one
that we just created which is new to do
okay now so now we have you know II to
read the contents out that file and you
know it you know pace right here when
you could drag the key this as well
driver equal to SQL spear server
semicolon server equal to the server
name semicolon and then you know let me
copy all copy all that and let me put
that you know here and you can see me do
this it's easy to understand so this is
the content of that particular DS and
DNS file and I mean to say not DNS file
but DSN file that's the content you see
that's a driver server that's a UID and
then that's a trusted connection equal
devices that use windows authentication
and then UTF base that's the system name
and then that's the database name so
nothing more than that so so that's what
is here then we need to give an SQL
statement to work with let me go back to
sequel studio and copy the sequel
statement and running 34 so we have 34
records in customer table let's start
the last name starts with who we let me
pierce that's SQL statement there and
don't finish and now you know it says
that 34 and if I do okay saying you know
this is the way this works is again you
know you need to parameterize if you
want to let me go and run this script
real quick because it
constant rally r34
it looks like it went through just fine
and you know it was successful let us
make will change for not number one we
will parameterize this thing going to
the cell click this button here it's no
constant value we'll use a parameter and
give it a name it's we're working with
table customer underscore last name
underscore V and score column and just
giving some description count okay okay
so let's let us go ahead and run one
more time just to make sure that the
parameterization that we just did you
know it's okay with the whole thing so
if this goes well then we'll tweak the
database in the back end and we'll force
this script to fail and then we can look
at the results and review so so no
issues there passed and it's just fine
let me close the results and we know
that this works and it is expecting 34
when it goes to the database and does
occurring let us go to the database and
here as you know when we run the script
you know we have 34 rackets that has a
last name starting with week so let's go
to the data and that's the last name
that has put a V right in front of it
and two records last name so now if we
don't need to do that if you go here and
run this script we have 36 I know that
means here we are 34 but we are 36 that
means some change happened to the
database somehow
if we run this script you know
technically it should fail right let's
see if it fails or not because now the
data sheet the global data sheets is
that they should be 34 records but there
are 36 records so it should fail okay
that's a good sign
it failed that's let's take a look at
the reason so it's little cross mark and
it says it failed and you know 34 34
where it failed but there's nothing here
so what you need to do is double click
on this then you get this window
this is expected about is 34 but the
actual value store is 6 because we
manually made a change so we need to
increase the number of record count
further for the last name starting with
V so there's a you know it had a value
of 30 for it but it found the value 36
that's the difference so it failed
that's how you you check it now when it
comes to real time again as I said you
know as they always say it all depends I
mean now that you know that you can get
information from the database and you
can compare it so you can you know if
you have access to the database in in
the field and you can you know let's say
the one classic example that a lot of
people do at least to begin with before
doing any kind of business logic is that
they would always be a table at least
one or two tables you know that that
houses all the environment
configurations you know say for example
if it's a banking it'll be like name of
the bank address location you know all
you know e be a roaring number and all
that and this is a good example where
you could add a database check points
where there would be one script would
fill which will verify all the
configurations in the database when I
say a configurations in the databases
are
location configurations so for a banking
website the bank name address branches
their addresses all that is in the
database so you can verify all that
using database check points but you know
in order for you to do that a few things
about one you need to have access to
your database number two you need know
the schema you need to know that you
know they are know the schema then it's
a scheme I mean the table structure and
columns and all that and next thing you
also need to know to write queries so if
you can do if you can write queries have
access and know a little bit of this
about the banking schema that or any
database that you're working with in on
in the field then you can definitely you
know I had a database check points to
your scripts well that's it about
database check points and I will see you
in the next video
thank you for watching this video
thank you