Scheduling Multitarget Test Execution with Test studio Video Lecture | Telerik TestStudio:Automated Testing made Easy - Software Testing

in this video I will show you how you
can manage your test execution how you
can execute different set of tests
against different kind of environments
and how can how you can schedule your
test lists and your tests so first of
all when you're ready with creating your
tests you need some container for all
the tests depending on their area or
depending on the feature or whatever you
use so that you can execute those those
tests and those test lists separately
according to your automation strategy so
here come the test lists you can create
static test lists which include exact
exact tests or exactly selected tests so
you can select dynamic test list which
includes dynamically adds tests
according to rules for example the name
should contain verify and contain verify
and you see that those two tests will be
included in this test list after that
after you create test lists
have this one you can create different
test lists for for different kind of
tests for example if you have tests that
are done exactly for your staging
environment and tests that are done
created for your wife environment you
can create test lists that will include
all the staging and one test set
includes all the staging and one test
list that includes all the wife
environment tests and you can of course
execute those separately but here comes
not a very good feature which with which
you can select on which environment to
execute your tests without creating any
additional test list so this is my test
and this might navigate step so in my
navigate step I will just navigate URL
and I would use base URL see here that
my base URL is my server one and my
navigator you know is my test page so
the whole URL will be HTTP my server one
slash my test page for example if I have
another second server which has
different configuration I can set on a
test this level this setting the base
URL so for each test list I can specify
which server to be used for my base URL
so if everything else is the same
I can only change from my server one to
my server two in the other test list and
the tests will get executed on all the
servers in that way so if I change my
server to for example this is my staging
environment those tests
automatically start executing and on my
staging environment and in that way with
the same set of tests always changing
the base general property I can execute
those tests on different environments
another step is the actual test
execution test to do provides a very
good scheduling feature which enables
you to run your tests on different
testing agents on different machines so
here I have connected to my server to my
scheduling server I have and on this
schedule server I have connected to
agents so these are my execution servers
I can collect as many as I wish you can
see the statuses of those this one says
it is dead because it's disconnected I
will go to my other machine now and when
I see that it's that I can go to my
other machine and very quickly power it
up
so Cisco see now it's a wife is how you
can maintain your testing agents and see
what exactly do what browsers do hear
from them and execute your tests CRO
cross browser of course so when I have
my connected agents
I can run remotely directly right now
run my test lists or one test list or I
can use scheduling feature if I want to
run remotely I have these options to
select on which agents to execute the
tests and I can execute all test lists
and all tests from a test list on all
the machines so let's say if I have two
specific environments I would like to
execute all tests on both environments
let's say the operating system is
different I can do that in that way but
if I have many tests that need to be
executed only on one environment they
have two agents with this same
environment I can use this option
distribute tests among these machines
and the tests for my test list will be
distributed among the machines so this
will speed up my execution much and this
is very useful if you have many tests
and if you want to execute those tests
faster of course I can schedule tests if
I wish I can create recurring runs and
monthly hourly means daily whatever you
need if I'm connected to source control
to TFS I can connect the scheduling
results to the TFS so that the
scheduling the execution to TFS so that
it will pull the latest version of my
project from source control and I can
select when where I want execute which I
agents I don't execute my tests
I can send email after execution the
always or depending on the error I have
these options to select when to receive
the email exactly and I can customize
this email and edit edit the subject the
body and everything of the email and now
I can send different kind of attachments
with the report of the that run so in
the results you can see that I have this
gadget run and when it gets executed it
will update the results will be updated
here I have some other runs so in this
calendar you have history of your
execution runs and you can see which
felt which passed what what were the
problems and what were the exceptions
and I can see the walk and see the the
exceptions in my tests so this these
test lists are very useful to manage
your environments to match your tests so
that you can run different versions of
your tests against different again
different environments depending on your
base URL or you can also distribute the
tests between many environments in order
to speed up the execution or you can
execute all the tests on our environment
so that you can cover all your use cases
this is our in-house scheduling and
execution feature of course all of our
products API testing weapon desktop
testing and mobile testing have their
own command oner that can be used in
continuous integration systems so that
you can execute the tests inside your
continuous integration over