Accelerate Your Test Automation with Test Studio - Webinar Video Lecture | Telerik TestStudio:Automated Testing made Easy - Software Testing

thank you all for joining today's test
studio webinar this is Andy Weiland I'll
be conducting today's demonstration
along with illion pan chef today we'll
be talking about how to accelerate your
test automation with teller test studio
by progress both
just a few housekeeping items to mention
yes today's webinar is being recorded
and it will be made available once it's
been rendered also all callers are muted
throughout the sessions so please be as
loud as you'd want and for anyone
seeking help for with goto meeting or
have any questions along the way please
feel free to use the chat panel or the
questions panel also today we love to
hear from you through Twitter if you'd
like to please tweet us and just hashtag
us with HS studio and we'd be happy to
answer any questions you may have
through Twitter as well first by way of
introductions my name is Andy Weiland
I'm a manager of the sales engineering
team and a certified scrum master and be
working with test studio for quite a
long time over six years at this point
also working with me and helping us
today present is our product manager
illion pan chef hey everyone
I've been on the team for more than six
years as a QA and now as a growth
manager so I'm happy to be on this
webinar so today's agenda we're going to
be talking about where you are now today
with automation or maybe without
automation and of course what test-video
brings to the table and our all-in-one
testing solution how you can integrate
collaborate automate and accelerate your
test automation for beginners or wizards
whether you're a pro or whether you're a
non-technical user we empower all of you
to be able to automate and of course
we'll be demonstrating the product a
little bit here I'll be focusing on the
telluric translators and working on some
dynamic grid automation and allianz
gonna join us in later as well to show
us how API tests can be used inside of
web tests and overall strength in your
automation strategy also he'll be
hitting some topics on the roadmap so
many company companies come to us from
one of these two areas and many times
it's from both actually at the same time
and sadly sometimes neither teams that
are involved with test automation
strategies know that the other ones in
paint and these two are really from a
manual testing where maybe there's no
automation and place this point
from what we call bloated co2 testing
where test automation has become such a
large product or project to keep up with
it's taking your developers away from
the application right so either way you
go whether your manual testing where you
whether you have bloated coded testing
it really tends to fail agile right so
here's a happy sprint this is where
everybody wants to be right this idyllic
utopia where everything is is perfectly
in harmony you've got your backlogs
moving along you've got your sprint
planning meetings you've got your
product owners happy your scrum master
is taking care of the scrum team you
know things are churning out and
everybody's happy right but you know
what they say about agile agile doesn't
fail you you fail agile and where does
it typically fail in in testing and as
the application grows testing grows
exponentially so manual and bloated
coded really can't keep up in this type
of environment so what tends to happen
is suddenly you have an O sprint instead
of a happy sprint you can see the
testing is kind of swelling out of
control it's throwing off the
deployments the initial you know the
backlog is starting to get jammed up as
well so we have a little bit of mayhem
you already see some of your best
developers are kind of falling off their
a-game and things are becoming a little
problematic and even the product owner
over here seems to be disappearing and
then before you know it it's all hands
on deck emergency meetings everybody
come in to right the ship you know the
test hasn't testing has now infected
everyone so this is the software
equivalent of zombie apocalypse right so
where do you want to be how about a
mature framework that can rival selenium
and does and essentially starting the
day by reviewing test results in your
email from test list that are scheduled
to run overnight or that are may be part
of a build process and a CI integration
you could really focus in on what failed
rather than wasting time trying to
figure out what works and then of course
when you find issues test related issues
you
can quickly jump in and modify and
update those tests and evolve those
tests you know quickly rerecord or re
execute things application issues you
can report them directly into the bug
tracking system and create a feedback
loop between your QA s and your
developers right so testing it really
aims at not just one persona but both
having the ability to empower the manual
testers and non-technical users out
there with a very easy-to-use record and
playback capability and releasing your
developers from testing hell effectively
now test studio is not just a framework
right
it certainly starts there but it's
rather more of a workshop built on top
of a framework with so many tools in it
to help you find your testing balance so
I'm going to take you in and show you a
few of those tools here in a moment but
a few things to look at before we go
test video gives you many different
components to build out a test lab
environment and to integrate into your
systems and processes so whether you're
a developer or tester you could check in
the source control and keep track of
versioning you know you can integrate
with your build and CI processes you can
have execute across multiple agents with
our runtime licenses many times virtual
machines and so forth you can analyze
data from the application servers the
database servers with our application
monitoring capabilities in our
performance testing and our load testing
as well you could really build out a
really nice environment where things can
execute and be executing and be very
resourceful in keeping your automation
going this is the key to keeping that
testing swell under control as having an
automation process that can continually
deliver for you now ease of use in test
videos number one that's why people come
to us again with lots of times we have
customers that are coming from manual
testing that really don't do automation
they're non-technical users that's
certainly something that we dealt with a
lot and we really built our standalone
environment for those non-technical
users with
a powerful record and playback
capability and in many ways to maintain
the test over time without the use of
any code necessary but of course the
ability to extend it in code convert to
code use our built-in IDE if you'd like
or step into Visual Studio where you may
be living all day already and use our
visual studio plug-in so we have
endpoints for everybody to access tests
to do we have collaboration between bug
tracking and source control so that
everything stays centralized for you and
the ease of use just makes it
approachable and usable by maintainable
for the long run as well what do we
cover with test video from functional
testing to manual testing to low testing
to API testing mobile testing
performance testing one thing that
you'll see throughout some themes that
you'll notice is again that ease of use
the ability to really reduce or lower or
potentially even eliminate most the code
involved in the test process and that
means not just creation of tests but
maintenance of tests over time the reuse
of functional tests to run as
performance tests or to run inside of a
load test so you get a lot of mileage
out of our tests as well and of course
our unique element fine logic strategy
you'll see makes these tests stand up
over time and cross-browser compatible
as well don't forget mobile testing of
course your native hybrid mobile web
applications on iOS or Android you so at
this point I'm going to jump over to my
demonstration of tests to do and what I
have here is a project that's got some
kendo crud operations so this kind of
crud tests basically a first of all
showing you what we call sort of
modularizing your test cases and this is
a master test that's effectively using
one of our most popular features tests
to step to call a sub test so I have a
create sub test an update sub test a
delete sub test if we double click into
these we can open up multiple tests and
multiple tabs here and kind of move
through them and back and forth we can
see this has a navigate step got some
maximize browser window there it looks
like some data entry for us as well and
a final verification at the end every
good test should have some verifications
in it
this one could even use some more than
this but at least we've got something at
the end to make sure it's succeeding
then our master test goes into the
update process in the same grid and here
it looks like we've got a verification
that's continued on failure so no matter
if it fails or not we'll go ahead and
move on and then it's going to execute a
sub test within it now this sub test
actually has its own data set so this is
going to naturally loop as you can see
there's three different item names in a
built in data set in what we call local
data you can also of course bring data
with you from all sorts of sources
whether it's a flat file or live
database connection and you can bind
those to your tests as well so here's my
data source that's gonna run this in a
loop form and essentially update
multiple items in the update process
within the sub test and back to the
master then we go through our delete sub
test here
here have some verifications that
kickoff at the beginning one at a grid
grid level there you can see the
translators that are built into test
studio can automatically identify when
it's a teller control like a kendo grid
and oftentimes you get some bonus
features when you're working with our
own controls of course we do support
third-party and custom controls too but
when you get to teller controls you'll
see there's some added bonuses there so
this sub test actually uses a while loop
this is conditional logic from our
conditional logic menu things like
if-else while loop and loop in this case
we're looking for a certain item in the
grid in a dynamic situation going page
by page until we find the appropriate
item bear in mind that this is after
we've created some records and updated a
few of them along the way so things are
going to move around but basically at
this point we'll go through that delete
process and we'll be back to the
beginning essentially so we're gonna run
this test no we do have ways of slowing
down test execution and debugging during
the execution I'm actually going to turn
that off so we're going to speed up the
execution of this and we're gonna run
this one here to begin with
in Firefox but as you can see you can
run this test actually these series of
tests if you will across any of these
five browsers these tests are made to be
cross browser compatible I'm gonna hit
Firefox here to begin with and we'll see
how we do
so our kendo master test kicks off first
of all
at the bottom right you can see the step
count and what is going through at this
point time you can also pause if you
needed to along the way but here's our
initial create process entering the data
here into this kendo grid this is of
course a jQuery kendo UI grid and now
it's going through the update process
this is now using that loop this is that
subtest that's looping through and it's
actually finding each row within this
grid not by a position but based off
some of the content so it doesn't
necessarily have to go in that
particular order and here we have page
by page very quickly looking for I poke
coffee with the while loop process and
once it finds it it should go edit that
particular item and delete it and then I
went back and it deleted the very first
item that we added in the create step so
there we have a completed crud operation
in three different sub tests run by a
master test all of this done with record
playback and what we call basically our
codeless format of a test studio test
there's lots of settings and things that
you can do inside these tests timing
adjustments that you can make you can
add tons of verifications through our
recorder and element highlighters
there's just a lot of sophistication
here a lot of things that you can do
again without necessarily having to use
code if you need to at any point you can
always right click and edit and code as
you can see I've got a test step here
that's been edited in code and when you
do that you can also not only do
generate a code behind file which you
could choose between C a c-sharp and
vb.net for your for your code as well so
here I have my code behind file you can
see where I've converted a step to code
the beauty of this is that you can
really minimize that as well you don't
necessarily have to convert everything
to code if it's just one particular step
and that allows for those non-technical
users to continue to maintain those
other portions of the test code lessly
until it's necessary or if it is ever
necessary to to convert it to code and
extend it code but again I should
mention too in our IDE built in here you
do have some great intellisense that
will help you really construct your test
steps no visual studio required here and
then again for the developer testers
there that are working in Visual Studio
we have the visual studio plug-in so all
these things were going through in the
standalone environment you can do in the
visual studio plug-in as well I'm gonna
jump into one more thing just to show
you a little bit about this sub test
that has its own data-driven component
to it now normally when you data drive
something like a verification for
instance that's going to be something
you can do directly from our properties
panel on the step in question and of
course we do need a data source for that
well since this test already has a data
source built into it I can access that
data source directly from this drop-down
this did this drop-down is going to list
me any data that's collected along the
way and what we call extract where you
can actually grab data from the live UI
so possibly in my create step if I
generated a unique value I might want to
extract it and bring that into my update
step my delete steps of this these tests
but here I can actually data drive
something at the surface level so this
would be two data drive the actual text
or in this case we're doing a
verification so we're going to data
drive the verification for that
particular step and once I hit set
that's it so this is more of a surface
level verification well this test did
loop but as you can see prior to me
doing this it didn't have a visible
surface level verification there which
would either be a verification or more
of a text entry kind of step right so
nothing happened at the surface so that
data-driven portion of this test is
actually happening here in the click
edit step so I want to show you real
quick as you can see first of all when
you click on a particular test step it
always highlights the corresponding
element for you in the element
repository we can right click on this
element we can go in and edit the
element if I wanted to I could spin up a
live version of the UI and attach to
that and edit it live in the UI I'm
going to do fine without connection
really quickly just to show you some of
the design and some of the
sophistication within test Studios
identification strategy so this shows
you that when it gets to this particular
inline editing grid and goes to click an
item to edit its finding the item and
the edit button not based on location or
path or anything like that test EO is
able to use
there's multiple layers here to look for
the appropriate grid the row inside that
grid and then the edit button for that
row so based on this we are using the
intertext which is the value within the
row and we've used a contains operator
and instead of the initial static value
I've fed in the item name so that it
will iterate through our three different
selections in our data source from the
local data table and that's what gives
us our loop so when you add data to a
test of step it will naturally loop so
that's why I back here when we got to
the create and then the update we had
this sub test naturally loop three times
through those different data sources and
and then follow out into the delete
process one more thing I'm going to jump
in and show you to is just a real quick
get into the live record mode so we'll
use a function called run to here you
also get run from here and run selected
steps once you're in the live record
mode but this run to here will execute a
test up to whichever step you choose and
then it attaches the recorder will step
into the ie won't record it here real
quick you can record an ie Chrome or
Firefox and you can mix and match as
well so there's no restriction to that
but I wanted to show you really quickly
when you do get into record mode and
you're working with a great like this
you want to turn on your element
highlighter and view that grid through
the lens of test studio using the
element highlighter you can really see
how test studio sees it so here we can
see that it identifies first of all that
this just isn't a grid it's a kendo grid
so the translators kick in we do have
translators for generic and you know
other technologies as well so it can
identify a generic grid in fact you can
see a generic HTML table layer that's
identified here and some cool functions
that you can do from that but when it
comes to a kendo identified grid for
example you can see our quick steps list
oops let me get back to that the quick
steps list here gets pretty lengthy
because there's a lot of extra things
that you can verify without even having
to exercise the grid so a lot of the
settings that go into setting up that
kendo grid are
suppose through that translator and in
addition to that the ability to identify
and automate these controls are all done
through those translators as well all
right so lots of cool things that you
can do with the element highlighter here
you can see it identifies a cell within
a row within that grid so we have that
layering in that extrapolation and all
sorts of different verifications you can
build in here JavaScript events you can
fire as well scroll actions Mouse
actions like hover over and right-click
and then of course you if you'd like to
you can jump in and use the toolbar
below with build step and the Dom
Explorer below and all sorts of
different actions and verifications down
here as well so lots of building tools
lots of ways to make very advanced steps
things like even element to element
drag-and-drop operations can be done
with this recording toolbar so lots of
capabilities here for the beginner to
the developer tester really we try to
make it something that can be approached
by many different levels of users and
all can be able to add to the automation
solution so that's it for my time I may
handed over to Ellie on Ellie on take it
away thank you Andy today I will speak
about UI and API test integration inside
test to do this is new feature from our
latest release and it's something I
would say a little bit more advanced but
yet it's easy to do and can be very
beneficial for anyone who is doing UI
test automation so let's first start
with some issues that we have with
automated UI tests they can be slow
doing everything to the UI depending on
some desktop actions can be slow they
can be unstable
yes test 2 has great element
identification but yet changes can
happen to the UI the Dom tree can change
new elements going inside some other
elements
moved out of the application some
dialogues or unexpected UI elements
appear and all these can break your
automation that goes through the UI so
sometimes of course the panic on how you
do your UI tests they can be unstable
even even if they have done according to
all best practices other other problem
other issue that we may have is that I
want to validate one let's say button
but in order to get to reach that button
I have to go through a walk-in page to
several other pages to form or something
like this and to test the Z I have to go
to x and y and this also is not very
efficient and again can be and will be
slow and sometimes not very stable and
something but something interesting is
hard to simulate concurrent sessions and
can simulate several different users
walking walked in to your application
and doing actions or anything else on
the same page at the same time doing
this through the UI can be hard when you
have one test doing something on your
page you have to walk walking with
another user on our machine or maybe
another browser if if this is done
through the UI and you have to do the
syncing very well and this this can be
hard to achieve through to the UI so
what what solution is its API tests and
API calls so for the first problem that
tests can be UI test canvas wall API
calls are way faster they don't go
through the UI so if you use them they
can speed up your tests tremendously
a pair calls are more stable of course
because they don't rely on the UI don't
don't worry on the Dom tree they don't
rely on all these elements that
sometimes can break some sometimes if
you want to reach Z you can skip some of
the steps before that and for example if
I have to create a user if I have to
login if I have to create some testing
data I can do that through the API and
skip the UI for that so you can skip a
lot of those Hicks Y steps to reach the
just making the test more stable and
faster and for the most issues
API calls again when you want to do
something with the back end while you
are walking at the UI you can do that
with the API call and just verify what
happens with the UI
now let's move on with the demo I'll
show you quickly how this integration
between UI and API web tests happens
inside test to do so I have my test
studio opened here I'll create one web
test we'll be using a testing
application that is actually a bookstore
where you can log in you can create your
user login see the available books and
purchase one of them let me first start
recording our test I'll be using Firefox
and this is our application it will bolt
and test to the recorder will attach to
the browser first of all I would like to
register a new user here but this is not
the goal of my of my test I don't want
to verify the UI of the register of the
registration of user
that's why I will do this through the
API here instabuilder in the common
section you have API test aesthetic
option when double click it you see the
available API tests inside our web
project each test to do project has
embedded API tests in it API tests
project actually so here you see what
what we have now you can open that
embedded API project and edit or add new
tests or delete and everything will be
updated here so all the tests that we
have in your embedded API project can be
used in web tests as as steps we can of
course import existing API test if you
already have used tester for AP is a and
if you want to reuse some of those tests
here by clicking this one test to do for
APS will open and now be able to edit
those tests so they are already done but
I just want I would just want to show it
to you
to see how easy are how simple are they
first of all I'll use the create user
test it has one request that is creating
the user and two more steps that are
actually getting the authorization token
which I'll be using in my other tests
depending on your security you can use
simple authentication or also 22.0 or
you can get access tokens as I'm doing
this here so I'll use this test API test
I'll put it in the beginning because I
want to create my testing user in the
beginning of the UI test
I'll execute this API test through tests
to do for api's because I just want to
create the user here of course later
when I execute my web tests everything
will happen automatically because I have
this here added so the testing user
should have been created it is test one
with password test one sign in and we
signed in I will add one step which
waits for this element and verifies that
this element is visible just to be sure
that we walked in correctly now I'll hit
this button and here is the list of the
books that we have at the moment first
of all I want to verify if another book
is being added while I'm at this page if
it's going to appear here so I can do
that through the API again I have that
test which creates a new book I run it
it will add a new book to the list here
it is escape from freedom so when I hit
refresh here in the UI it should have
appeared here it is let me add this test
which I just executed to our web test so
that everything happens automatically
next time I run this web test again I'm
addict adding API test as a step this is
the create book one here now let me
first verify that this appeared so I'm
adding this step which waits for this
element to exist so that I'm sure that
after the API test this was created
and the UI has been refreshed correctly
adding the new book I'll open this this
book and here while the user is watching
at the description or wondering should
should should he or she buy the book I
want to change the quantity of this book
now it is one I want to change it from
the back end to zero so that we seen
rate that someone else just purchased
the last copy of the book again we are
doing that through the API so we have
that order book test which is just one
simple post request and it's just orders
that book I run it from tester for api's
it passes and I will add that in my web
test as well now when I have purchased
the last copy of that book in the UI it
still says quantity one and now try to
order this one book when I hit the order
button we receive the expected error I
will verify verify that this appeared I
wait for this element to be visible
I would like to verify the error message
I'll do the verify the verification this
text and I'll hit the ok button
so we've done our test we verified that
when one user is looking in the book and
the other user purchase purchases the
last copy of that book the first user
will get an error message and how he'd
walk out at the end
this is what I have in test to do I have
recorded all the steps I have added my
API tests that do the proper API
requests and at the end of this test I
want to do a cleaning of my environment
and you can delete users books or
refresh everything I will delete the
book that I already created I have this
delete book test here and in tested for
api's I'll also run that test to see
that it passes yes it passes it just is
just another delete request that removes
the book through the API so what I have
done in this test
first of all with one simple API test
I created my testing user then as a
normal regular test to do web tests I
started recording I walked in with that
user
I did some wait some verifications I
went through to the book that I wanted
to test and to purchase then I added
that API test which depletes the book
and makes the coins from one to zero and
at the same at the same time when I
click the oak the purchase button
through the UI I receive the error
message that this book has already been
sold out which simulates the multiple
user scenario and at the end of the test
I do a quick clinic of the environment
deleting that book so let's run the test
and see what will happen although I
recorded that in Firefox it can be run
in IE chrome or edge without any
additional adjustments the usual have
been created we walked in created the
book refreshed and suddenly the book was
out of stock and this is how easy is to
simulate this scenario which I would say
is pretty complex one and without those
API tests it would have been a lot more
complex to do it through the UI and lot
more slower and less stable before I
continue with few words about the
students roadmap I want to make sure
that you all know about our book where
we each week post different blog posts
technical blog posts about features and
not only explaining how how for example
to use wall testing the demo that I just
did with our autumn off sophistication
and with more technical details we also
post it as a blog post and this
bookstore demo application will be also
posted there and the demo project so
that you can just download it run it on
your local machine and play with it I
want to remind you once more that you
can ask questions on Twitter with
hashtag hey studio or in the questions
pane that you should be seeing on this
webinar after the after the webinar will
post you send your email and we'll post
a blog post with the webinar recording
and we'll answer some some of the most
interesting questions in that book post
so please ask
questions and stay tuned few words about
Tesla's roadmap for this year we have
one major release remaining the most
interesting things in that release are
our intelligent assist execution team
which incorporates sub couple features
the automatic rerun of failed tests so
if there is a failure because of some
unexpected dialogue or some environment
synchronization failure in
synchronization stuff like this
something that's not a book you can set
this automatic Arang of failed tests and
on the second goal they may pass so that
they will not mess up with your
reporting and your results at the end of
the test list we'll add visual recording
of tests list execution so that when you
have a failure you can just go on and
check out the video and see what
happened prior prior that failure and
what led to that failure will be in we
have this pretty common request for our
scheduling feature to persist the email
settings so we'll do that we'll also add
a new verification step which we'll keep
an eye for JavaScript errors and we'll
alert you and we'll fail the test if
there are new JavaScript errors and or
some JavaScript errors that are not
expected for next year we have also very
exciting and ambitious plans wind-up
here are some of some of the features
that we are planning there a lot more
everything is around helping you craft
your tests easier and making them more
and more stable the first thing to
mention is the interactive maintenance
assistant which is something that
through the improved
search will suggest how to fix your
failing elements if an element is
missing or the finding has been broken
test two they will be able to suggest
you how to fix it or to fix it instead
of you automatically this does making
tests more stable and way more easier to
maintain next thing is the image based
element detection this this again will
make the tests more and more stable for
example if you have elements with
dynamic IDs with our auto our current
find logic is very good there are some
cases where it it can be improved for
example when we have dynamic IDs for an
element and imagine if you had the image
based element detection which detects
the elements not by their final object
and by their position in the Dom it
takes it by an image that you take of
that element so the combination of both
approaches for element identification
will make that's very stable and even
the hardest applications to automate
will be a lot more easier to to do
automated tests on next thing to mention
is the code base test execution which
means that you will be able to execute
your tests on different environments in
the cloud
discovering different kind of browsers
or operates on operating systems and
then receiving your the results on your
machine ok that that was from my side
since it seems that we have a lot
questions in our chat panel and we have
some more time of the webinar I'll leave
it open for about 10 minutes so that you
can you can you can ask us your
questions and we'll be answering
there in the chat or on on Twitter