Extending Tests With Code in Test Studio Video Lecture | Telerik TestStudio:Automated Testing made Easy - Software Testing

hi i'm jim holmes and i want to show you
some pretty exciting new capabilities
for working in code inside of tests to
do this is new from 2016 r1 and there's
a lot of really great stuff here that
can help you extend tests to do extend
your tests and tests to do to be much
more solid much more accurate and a lot
more maintainable so this is pretty cool
let's go ahead and get started first off
let's have a look at what we're gonna be
interacting with you may have seen this
demo before it's just a very simple
contact grid the idea is that via
Kendall UI we can create new users here
new contacts we can work at editing and
updating those if so we can build some
very simple crud tests or create
retrieve update delete so here's what a
standard test might look like and in
this case we're actually doing an update
test so we need to have a contact in the
database we need to retrieve it then
we're going to update it and persist it
back and if we run it we'll see that
this will run in the background and it's
going to run just fine but one of the
problems with this is that we're using
the UI itself to set up the data for our
update test and this becomes a problem
because if we have some issue with how
the test was how the create part worked
the rest of the test would fail moreover
if you're using the UI to set up and
configure and create your test data it's
slow and it's brittle so there's a
couple things here first off and most
important in good test case design we
want every test to set up its own test
data
secondly we want to avoid the UI so this
is an okay test but you know like I said
we're using the UI to set things up
notice any other problem we're verifying
at the UI level but we're not actually
checking the database we're not making
sure that things are properly persisted
down to the database shown away this is
a very shallow test and it's not a great
test which is why if you'll notice it's
named not a really good test we can do
better and this version a test studio is
gonna help us out so here we're moving
the set up for creating the contact off
to a coded step we're also going to make
use of some external libraries so here
is an idea where you can collaborate
work together with your developers to
build up really terrific support
libraries that you can leverage to do a
lot of really neat things so remember we
want to be able to create a new contact
but we don't want to do it from the UI
we want to do it from code and moreover
we want to actually use the existing API
of our system to build those things out
why because as a team we've built those
api's we've tested them we know they're
solid so let's go ahead and use them for
our own tests for other things how do we
do that
so here is a file that is a an API that
I've built working with the developers
and this is intended for testers so
there are a few specific things that I'm
interested in as a tester I want to be
able to easily create new contacts
I want to I've got a couple helper
things here
for randomizing but here also is
something I want to get an entire
contact by its ID so I can create
contacts to do the setup and then I can
reach out to the database to test things
now here is one really neat piece here
there's a great open source library
called faker and it's available in a
bunch of different languages my point
being that we're using this to randomize
the contacts that we're building so
we're gonna get unique data every time
and moreover the faker library does kind
of realistic stuff okay I'm not going
off on a huge tangent there's a point
here inside of test studio we can
leverage all of these libraries and we
can do it really easily so we've got a
number of different things that we're
gonna have to bring in to test studio
let me show you how we do that so the
first thing I want to call out is I have
created this library folder here and
inside of that I have copied the files
that I was just walking you through
there's the faker library here's the
support library that we're working with
and then this Web API is the actual
project library or DLL that contains
some of the data objects no don't worry
about that it's easy to deal with so
we've got these physically located in
our project folder we actually need to
add them to test studio and let's see
how to do that
under test studio settings we're going
to go to script options and I can add
reference here so I browse to where
those files are located at I select them
and I'd add them in when they're added
in you can see that they appear here in
the reference listing here now we need
to actually start writing some code so
what I do is from the step builder I can
add a coded step here and the very first
time that I do this test studio is
actually going to ask you what language
you want to use you can choose C sharp
or Visual Basic I'm using C sharp in
this project
now you're gonna select a new coded
function and it'll drop that in there
I've actually already written this so
let's have a look at what the code looks
like
here's the C sharp file that is behind
if you will the test studio file I've
added a using directive so that we can
make use of the helper API that we had
and then I've got three simple lines of
code here that are going to actually
make all of this happen for the setup we
are using that helper API to create the
new contact we're assigning the ID value
it returns to the variable we'll write
it out to the log file extracted values
are test Studios take on a global
variable if you will it's available not
only within code but we're gonna make
use of it inside of our test as well
here so here we go at the very first
step we've got our new contact created
so we're going to go out to the site
we're going to click the
edit button but notice that we're gonna
have to look this up based on the ID of
the new contact that we just created
because we're gonna have to click the
appropriate row here I'm gonna take you
over and show you another awesome
feature of tests to do which is
data-driven find logic so this edit link
here let's have a look at the element
repository we're going to edit the
element and I'm going to show you what
this looks like now you may have seen
some other videos of mine where I'm
talking about flexible find logic this
is kind of a play on that as well
we're starting by finding the table body
here we're finding a row which contains
the new ID that's an extracted value
here this is data bound now and you can
see that we're able to pull this down
and add a coded variable here and this
was where I added in new ID
remember that extracted value and ID set
that so we're gonna click that will
update it and then we're going to verify
again using that same approach to locate
the region cell this one here for that
newly created contact so let's see how
this runs and see if it all works I'll
let you in on a secret I did this
beforehand so yes it should work
okay everything's all green we've used a
coated step to create a new contact
we've saved the ID off and we're using
that ID in two different places so that
we can dynamically lookup the contact
we're also using that to dynamically
lookup the appropriate contact and the
appropriate cells to do our verification
create our data we're doing that
dynamically with a helper function that
gives us unique values every time but
we're still not touching the database
all we're doing is verifying at the UI
so let's take this one more step further
here we are with a much better test this
looks almost exactly like the previous
tests however note that we've got one
more coded step here and we're actually
doing verification directly from the
database so remember I have my helper
method my helper API and now we can
return the actual object that we created
once I've got that I can pull the region
that's the piece of we updated right out
of that and then we've got a simple
assert to make sure that what we saved
on the UI also updated in the database
let me show you a couple other great
features that have been added to enhance
the coding experience inside of test
studio first off notice that we can
compile all of the code files right here
if we need to update any project files
from disk we can also do that but we can
compile things straight away that'll
pull in references to those for example
the external libraries that we bought in
syntax errors are immediately called out
here so if I add in something bad and we
get immediate feedback here letting us
know that we have problems in our code
moreover if I double click on that it'll
take me back to the area where problems
work now this was actually on line 4 so
I can clean that up we get compiler
output here so that every time when
you're making changes it's constantly
compiling
in the background to let you know about
issues that are coming up so just syntax
errors or other problems there you have
it some simple changes in tests to do
that let you much more easily bring code
the right amount of code into your
projects to make your tests much more
powerful more flexible more accurate and
much more maintainable I hope you find
great use out of these happy testing bye
bye this is jim holmes signing off