Creating Your First Successful Test Studio Project Video Lecture | Telerik TestStudio:Automated Testing made Easy - Software Testing

writing a good first test is a critical
piece of getting rolling with tests to
do as quickly and effectively as
possible hi I'm Jim Holmes
I'm a testing fanatic I love automation
and I love tests to do I used to work
for telluric both as an evangelist for
tests studio and the director of
engineering it was a great job I love
tests to do I'm here to help you get
started writing a good first test let's
get rolling okay let's go ahead and
start up tests to do the opening
dialogue lets us get some help hey
that's me an old version of this video
you're watching right now we can check
for updates manage our licenses we can
create projects there's a list of recent
projects here and I'm going to open that
one this is test studio 2016 our one
that I'm using for this demo test studio
lets you rearrange windows and panels as
you see fit these are also all
collapsible so you can really customize
how you want your layout there's a
standard familiar ribbon bar to work
with that'll change as we look at
different contexts test studio also
plugs into Visual Studio which is great
when you need tight developer test or
collaboration you can take care of
complex coding tasks but still share the
same great easy to work with tests when
you get started with your first good
test and emphasize good there are a few
key aspects to understand about your
recording that will make your experience
a whole lot better let me walk you
through a few of those as your test
suite grows out you're gonna want to
organize your tests in logical groups in
test studio we can create folders to
help you do that
and what's nice about test studio is
that it does not get in the way of how
you want to organize how you might
desire to organize things some teams
like to work let's say their tests in
rolls so we might have some
thing like administrative tasks other
teams might be more concerned about
features other teams depending on the
environment they're working on might
have to trace back to broad requirements
so that you might need to do something
like that what's also nice is you can
drag-and-drop and reorganize your
folders and individual tests as you see
fit as I set up my folders it's easy for
me to add new tests here either through
the ribbon bar or through the menu here
and just like the folders I can give
good names for my tests on different
items there are a number of properties
that I can take a look at description
owner there's even more test properties
here that I can work with as needed I'm
gonna use the kendo UI web Sushi demo
it's a great web app looks really sharp
it's built on top of the Kendall UI
controls they're HTML Javascript they
look really sharp and it just makes for
a good easy walkthrough for a demo like
this here we are ready to record a test
I can work with a number of different
browsers ie Firefox Chrome I can also
work with Apple's Safari for Windows
however Apple stopped supporting that
years ago so I don't even mess with it I
never install it so it's not picked up
here to record I can pick any one of the
browsers I'm going to use Chrome this
time so the recorder starts up notice
here we need to enter our navigation
URLs here not up in the regular
navigation bar
so we'll start recording notice that
we're picking up actions back here I'm
just gonna add an edamame item to the
cart
notice that things changed here we also
got the click action now it's time to
start understanding how we can work with
tests to do to add in validations
verifications checks I'm going to select
highlight element and notice as I move
around the page different elements get
highlighted I'm going to verify the
quantity I hover over it and the context
menu pops up here with a lot of really
nicely organized actions that you can
make use of I'm going to take the quick
step verify the text content contains
one we can see the verification shows up
over here now there's another handy way
that we can get to work with elements I
can locate them in the Dom let me move
things around here I'm going to turn off
highlighting and I'm gonna get just a
little bit more real estate here so down
in this window is the Dom Explorer
there's the element right there and from
here you can see that I have
verifications over on this side I could
work with very simple content
verifications in this case I actually do
want this particular verification there
I'm going to undock pull this up a
little more and you can see that we've
got add step so I'm going to add that
step in and we get the verification over
here I could also work with attributes
on that value and a number of other
things to stop recording just close the
browser you'll notice that by Goethe bit
and I actually clicked on part of the
screen that I didn't mean to that's easy
to clean up remove the step the first
most important aspect of working with
any UI test is to understand how your
tool locates or finds objects or
elements on the page so let's dive into
that and I'll show you how test studio
can really help you make a solid
first test here locators are how tests
to do and really every other UI test
tool find things to interact with on the
page so for example I'm going to pop
open the developer tools for Chrome here
and there's a great inspector tool here
that lets me just like the highlighter
in tests to do lets me have a look at
specific items so here are the various
elements that are on the page and we
need to be able to find those elements
now the best thing that you can do is
generally look for something like this
an ID that's an attribute in HTML it's
not 100% perfect but it's the best
option if it's not something that's
dynamic and going to change ID is the
best method to use for location if you
can't find an ID on the exact thing you
need you could do something like use the
CSS class value that's here there are a
number of other types of attributes that
you could use you could use XPath which
is a structural query language that lets
you work with XML or well balanced HTML
to do things like go by position and
hierarchy XPath can be a little tricky
to work with but it's a tool that you
should be aware of additionally you
could also use telluric fluent jQuery
language which helps you find locators
or define locators rather you eyes
change workflows change so likely you're
gonna have to update your locators
here's a feature that I love about test
studio it's called the element
repository and it can save you a whole
lot of time in headache is you're making
great tests the element repository is
you can think of it kind of like a
central storage for all of the element
definitions so we're looking at
it's the elements pain I'm also gonna
pop open the properties here because
that'll show us some more information
about that the nice thing about the
element repository is that it is the
central location for all of your
elements moreover it's stored by pages
so each element is uniquely identified
for that specific page if you need to
change or update something it's one spot
to go and it saves you a lot of time and
makes your tests much more stable and
robust so locators are the first piece
of critical thing about writing a great
first test the second crucial aspect
that everybody has to understand is how
to deal with asynchronous actions so
asynchronous is via Ajax or other
similar technologies were part of the
page updates and there's no call back to
the server these can be a little tricky
to deal with but there's a number of
ways that test studio helps smooth this
out for you
asynchronous situations occur when part
of the page updates without the whole
page reloading for example when I click
this we can see that there's a spinner
going on and then later we get the hello
world text that didn't reload the entire
page just updated part of it now if
you're using something like selenium
webdriver this can cause some problems
because webdriver and many other similar
tools get confused they didn't see that
the entire page was reloading so what
happens is we get a failure because we
can't find things like the text or the
elements that we're looking for tests to
do on the other hand approaches this
much differently what happens is behind
the scenes there's a dynamic timer that
is waiting on that particular condition
or situation to show up in this case
we're waiting on the hello world element
to appear now if for some reason your
verification
your action didn't work out of the box
by default you can do things like change
the role of this to a weight and then
you can alter the parameters there are
also test steps that you can inject to
help the point being
test studio will help you out of the box
in most common Ajax situations so you
don't have to worry about the
asynchronous you just concentrate on
writing great tests okay
great you've got a solid first test
we've talked about locators we've talked
about asynchronous you've got a complete
running test now let's take the next
important critical step in any software
development or testing effort and that's
check your work into source control
let's put this test over in the source
let's go ahead and connect to our server
for TFS you can use IP addresses you can
use the host name we'll connect here if
you haven't authenticated you'll need to
they'll be the list of the projects
we'll go ahead and we'll connect to this
one notice that we're back to the
project you can see the green marks
there
those are checked out let's go ahead and
check in and commit those changes please
leave a check in comment it's a big help
for your team's a big help for your
teammates rather when you take a look
back at the project you'll notice the
lock symbol that's everything's checked
in we're good to go you've got one
running test awesome it's checked in the
source control that's terrific but as
your project grows obviously you're
gonna want to run groups of your tests
all at once test Studios test list
feature let you gather up tests and
execute them on schedule let's have a
look at how that works
you've got your tests built they're
running individually now let's look at
how you can group these into test lists
for execution for different coverage
types test studio lets you create two
different types of lists you can create
multiple lists you can run them locally
you can run remotely we're going to show
you how you can use recurring patterns
here to set up different operations now
here's the neatest part of this I can
set up a cloud of remote execution
servers I've only got two here I could
easily have a hundred I can distribute
my tests across those I can even get the
latest version of tests automatically
from TFS once I schedule those out it'll
go off into the execution queue and run
without any further involvement from you
so you've got your first test running
terrific
you've got it in source control you've
got it running as part of a list or
group of tests that's all great don't
let it end there test studio has a
vibrant community where other people
working with test studio can help you
out test studio has top-notch support
folks I loved working with those people
they're tremendous they've got great
experience and they are there to help
you out there's also lots of great
documentation blog posts there's plenty
of support material to help you with
your success so there you have it I hope
this video has been helpful to you I'm
Jim Holmes good luck with your testing