Scheduling in Test Studio works a lot like the Windows scheduling feature

Test Studio's service will let you schedule the test list to be run on remote machines as well.

Follow these steps to create, connect, schedule, and execute:

Create a Scheduling Server - the scheduling server keeps track of what tests to run and sends this data to the execution servers. The testing process becomes almost completely automated.

Create an Execution Server - the Execution Server is an instance of Test Studio Standalone or VS plugin version. An Execution Server is ready to use when you configure it and register it with your Scheduling Server.

Connect a Project to a Scheduling Server - once you've configured your Scheduling Server and successfully registered at least one Execution Server to it, you're ready configure a test project for execution.

Schedule Test List Execution and View Results - once you've connected a project to your Scheduling Server, you can proceed with scheduling a test run and viewing the results upon completion. 

Create a Scheduling Server:

Installing and Using the software:

 1.Before proceeding with running the software, there are a couple things to confirm regarding the computer you will be installing the Scheduling Server software to:The software MUST be run from a Windows Administrator account.UAC (user account control, Windows Vista/7 ONLY!) must be turned OFF completely.Microsoft SQL Server or SQL Express needs to be installed on the Scheduling Server.

If you do not meet the above requirements, the software will not launch or will quit immediately.

2.Click Start > All Programs > Telerik > Test Execution 20XX.X > Configure as Scheduling Server

note:Before Click Scheduling server administration privilege is must  

3.Start Scheduling server

4.If you receive this message, close all open (Standalone and VS plugin) versions of Test Studio out completely (if you ran the Execution Software first you will also have to close it). For the VS plugin version, this means quitting Visual Studio. Once you quit other open instances of our software, the Scheduling Server software can run and you can proceed to the next step

5.You will see the following screen:

6.If this is a local only test (within your intranet), check the box for Integrated Security on the right of the window.

7.Set the Server to the server in question. For our example, we have installed SQLExpress on the machine in question. Our server for the example is .\SQLEXPRESS, and we want to create a database on the server named WEBUITS. 

NOTE: If you are not using the integrated security, you will have to enter your username/password data for the SQL server.

8.Click Create Database. You will eventually see a message that states "The database is created!" Click OK on the message when you get it.

9.The Import/Export buttons at the bottom of the screen are usualy used when upgrading from a previous version of Test Studio. If your previous installation didn't use the default installation folder You will need to manually import the previous configuration in order to continue using it.

10.The next page contains the settings for the Service URL, email settings, and as well the ability to register the machine: 

11.Click on Register the local machine

12..Leave the output path at the default and click the Register button 

13.You should receive the following message:

14.Click OK on this message

15.Next, check the box for Configure Email (SMTP) Server. These are the settings that allow you to send the confirmation emails out to yourself that give progress reports on the results of the tests you have run.

16.Enter in the information for your SMTP server settings in the fields below the checkbox: 

17.Click Connect, then OK on the Connection Established message that comes up as a caveat

19.The Connect button should now be replaced with a Done button. Click Done.

After you click Done, the Telerik Test Studio Execution Server application will open. Do not close this application as it is required to be open for your tests to execute. If you want to, you can minimize it (it will go to the system tray). And that is it, you have your Scheduling Server now setup

Create an Execution Server

The Execution Server is an instance of Test Studio Standalone or VS plugin version. An Execution Server is ready to use when you configure it and register it with your Scheduling Server. Because of this, you cannot configure an Execution Server without a successfully configured Scheduling Server first.

You can also review our Telerik TV episode on Establishing an Execution Server for a video walk-through of this process.Many executions can connect to the same Scheduling Server (SS) – the architecture is based on the master-slave model. 

Multiple Execution Servers (ES) allow you to execute multiple test lists simultaneously.

Both virtual and physical machines can be Execution Servers. You can also configure the same machine to be both a Scheduling and Execution Server. Differences in operating systems between the machines running the SS and the ES are allowed. However, make sure there are no version differences – every ES must be running the same version of Test Studio as the SS.A few things to consider when choosing an ES machine:You must be logged on with an Administrator account at all times – you can disconnect from the ES but not log offEnsure the location of your test project is accessible from the ESEnsure your SS and ES are in the same domainConfigure your Execution Server.After successfully installing Test Studio, the Execution Server application will become available. You can run it from:

Start Menu->Programs->Telerik->Test Execution 20##.#->Configure As Execution Server

Click on “Register” which will open a new Dialog

Connect a Project to a Scheduling Server

Once you've configured your Scheduling Server and you've successfully registered at least one Execution Server to it, you're ready configure a test project for execution.

You can also review our Telerik TV episode on Connecting a Project to a Scheduling Server for a video walk-through of this process.

From Test Studio Standalone version, create a new Test Project and add at least one TestList.

All functionality related to scheduling will be unavailable at this point. You need to connect your Test Project to a Scheduling Server. Keep in mind that the Scheduling Server doesn’t have to be on the same machine as the instance of Test Studio you’re working with.

From the Project tab click on the Connect button:

From this menu you can connect your project to a Scheduling Server. Keep in mind that a Scheduling Server comes with the Execution Servers attached to it. When you schedule testlists from this project – they will run on those Execution Servers (you get to pick what testlist runs on which server). Your local machine can also be configured as an Execution Server.

Fill out the hostname and port of the Scheduling Server you’d like to use. The service URL will be automatically generated for you. You can still change it manually if you like.

Now click on “Test Connection” to establish a connection with the Scheduling Server. This should result in a pop-up informing you that the connection was successful. If it’s not successful you might need to check whether your Scheduling server is working correctly.

The last field is the “Project source location.” An Execution Server assigned to this project will access this location in order to use the required testlists. By default this is set to the current location of your test project opened in Test Studio on the local machine. If you plan on using remote Execution Servers (i.e. not located on this particular machine) you will need to change it to a network share. A network share will look like this:

\\stoichev\mySharedLocation\Test Studio Projects\TestProject5

Where stoichev is the hostname of the machine and mySharedLocation is a shared folder accessible from your network.

Schedule Test List Execution and View Results

Once you've correctly configured a Scheduling Server and you've attached at least one Execution Server to it, you can proceed with scheduling a test run.

You can also review our Telerik TV episode on Scheduling Execution and Viewing Results for a video walk-through of this process.

Open the Test List tab in Test Studio. 

If you have not created a TestList you can do it now. To add a new TestList, click the List button and follow the wizard.

Once you have a TestList you can schedule it. Click on the Schedule TestList button. The Scheduling Wizard comes up:

1. Select TestList.

2. Select Time.

First you need to pick the desired time for this test run. By default this is set to 5 minutes after current system time. You can also configure this TestList to execute recurrently.

Keep in mind that slight time differences are to be expected between the time you've picked and actual execution time. Please check out this article on the subject.

3. Select Machine(s).

This step lets you pick the Execution Server on which you would like to run the TestList. If the list is empty then you need to add at least one Execution Server (see “Configure an Execution Server”). Picking multiple Servers will result in the TestList executing simultaneously on all selected machines.

*Keep in mind that multiple TestLists can’t execute on the same machine simultaneously and there’s also no queuing for pending executions (yet). If two TestLists try to run on the same machine, one will execute successfully while the other will return a "Server busy" status and won’t execute. This can get a bit tricky; Because of the implemented architecture some TestLists scheduled close together will start executing simultaneously. To avoid this you shouldn't schedule TestLists too close together on the same machine.

4. Select Notification.

This steps lets you configure the e-mail notification you will receive on execution. If you don’t want any notification leave "Notify me" unchecked. If you check it you have to select one of the three options and also state at least one recipient e-mail address.

*Note: Notifications are sent locally from each Execution Server. This means that the Server needs the necessary permissions to use the SMTP server with credentials as configured in the Scheduling Server's configuration.

Once you close the Scheduling Wizard, the scheduled run should appear in the "Results" menu. It should be yellow indicating it's waiting to be executed. After execution, click the "Reload From Server" icon in the Scheduling ribbon. The scheduled run will change to either green (if it passes) or red (if it fails). Double click on it to see the 

Read More

Test Studio Software Testing Tool by Telerik

Build automated tests for your web and desktop apps. Test HTML5, AJAX, Silverlight and WPF apps, JavaScript calls, Telerik controls, dynamic page synchronization, client-side behaviors, complex UI virtualizations and elaborate XAML animations. Quickly convert them to performance tests to identify performance robbing bottlenecks.

Read More

Automated Testing Videos - Why choose Telerik testing tools

Automated Testing Videos:
Silver Light Automation
Test Execution and Scheduling
Overview
Testing Rad Controls
Advaced Technic

Click Link Here:  http://www.telerik.com/automated-testing-tools/support/videos.aspx

Read More

.NET Web Test Automation: Selenium vs. Telerik’s Test Studio

Overview

With agile practices getting more popular Test Automation is important factor in achieving continuous delivery. There are so many tools available in market for test automation. It includes both Open Source and Proprietary Tools/Framework. It’s very challenging as well as interesting to pick up best tool for your test automation. Many times I have seen people choosing Open Source tools just because they are free. On the other hand it also true that most of the proprietary products are very costly. It was also challenging for me to come up with best tool for Test Automation for my project which included applications in ASP.NET and WPF.

In today’s post, I would more talk about Web Test Automation and try to compare well known open source framework “Selenium” (http://seleniumhq.org/) and proprietary tool “Test Studio” from Telerik (http://www.telerik.com/automated-testing-tools.aspx). The prior one is framework using which we need to create whole sort of test script by writing code while later one is product with nice UI. Somebody might say why I am doing comparison of open source framework with a proprietary product? The answer is – ultimate we have to come up with solution that satisfies my “requirement”. So before going ahead I have to clarify my or project’s requirement. Solution should provide:

Automation of Web Application (as of now just considering ASP.NET application for ease of analysis).Test support on Internet Explorer, Firefox, Chrome and Safari

Less learning curve as my resources would be from Testing team and may not coding expert

Better productivity for creating new scripts so that it would not increase much cost for new enhancements.Better Reporting feature for easy analysis of failure scenarios

Ease of Maintenance.Overall Test Script creation and execution and maintenance cost (initial + resource) should be less.

Analysis.The first two requirements are straight forward. Both tools in context (Selenium and Test Studio) satisfy this.

The later ones are more subjective and many vary from project to project. Let’s discuss these in details one by one.Learning Curve

Selenium – To work with frameworks that mainly require script coding, developer should have knowledge of both script coding as well as test case development. This increases learning curve for script developer. Also without powerful UI support, developer need to rely on trial and error to find out bugs in script itself. I must mention here that Selenium has very good support from community and that is very useful.

Test Studio – It provides nice UI that helps person self-learning the tool. It also provides multiple views by which you can carry out your work. One can learn usage of Test Studio by view various videos available on Telerik site. Also you can ask for any help from support team.

Resource Productivity

Here I would like analyse ease of development of a complex test script by average skilled user.

Selenium – It has very good apis and skilled resource can develop script with better productivity. The usage of IDE in Firefox is limited. So for any test case one has to do sufficient coding exercise.  The coding itself is bound to follow its coding life cycle including debugging and sanity testing. Reading just steps as a story board is difficult in selenium.  Handling of timeouts, AJAX calls are the areas where developer can make easy mistakes. So quality of script will more dependent on experience of developer in selenium.

Test Studio – It provides complete UI based script capturing as well as modifications to script test. You can easily see story board that gives you better idea about your test case and steps followed in the same. Tool provides various UI based options for capturing element, comparing values against required properties. You can easily add data driven testing without much effort. Even logical and looping conditions can be easily incorporated using UI. Capturing of mouse and java script event is UI based. This gives lot of relief to developer and person can concentrate on Test Case logic or Business validation planning rather than coding or development. UI provides high speed in capturing element, comparing the required values and verifying the output. This is biggest advantage of Test Studio.

Ease of Maintenance

It’s an important factor where you have large number of test cases.

Selenium – People find it difficult to manage test scripts than creation. For small change also it might need to recapture whole script. It requires lot of planning for large scale project to use selenium effectively in there project. Tester needs to do debugging and find out where it’s an application failure or it’s a script issue. Many times dedicated effort has to be given to keep pace with changes incurring in agile sprints. 

Test Studio – Here Test Studio has upper hand. One can create modular test cases and reuse them in various test scenarios as and when required. It provides detailed failure log that includes images of failed step and expected step. So just by viewing image one can easily do initial analysis and decide whether script to be modified or bug to be raised for application issue. Steps list and Storyboard help even new developer to understand test case better way and one can do modification easily to the same.

Overall Cost

Let’s try to put together cost statics for say 500 test cases. The productivity of 3-4 test cases per day can be achieved for Selenium while we can consider around 6-7 test cases for Test Studio. I personally believe we can achieve much more than 7 with Test Studio. Let’s assume 20 test cases need to be modified or created for code changes per month that includes modification and enhancements to system.

Item	Selenium	Test Studio
License Cost	$0	$2500
New Script Development Effort with low productivity	167 PD (3 cases per day)	83 PD (6 cases per day)
New Script Development Effort with better productivity	125 PD (4 cases per day)	72 PD (7 cases per day)
Script change effort per month 70% change & 30% new	4-5 PD	2-3 PD
One Year Maintenance effort	50-60 PD	25-35 PD

So from long term perspective and with increase in no. Of test cases Test Studio not only pays you off initial cost but also saves the overall cost. 

Other benefit of using Test Studio

WPF & Silverlight

Test Studio support WPF and Silverlight application test automation.

Manual Script customization

The Test Studio generates code behind the scene which is based on Telerik Testing Framework i.e. Similar to codedui framework of Microsoft. This gives additional flexibility to developer it he/she at all need to write done manual scripts.

Performance Testing

The upcoming version (2011 R2) of Test Studio includes Performance testing with In-Depth analysis for .NET applications. I am eagerly waiting for this release.

Comparison Table

Below is the detailed comparison between Selenium and Test Studio:

Item	Selenium	Telerik Test Studio
IDE / Script Capture	Firefox 3+	Firefox 2+, IE 7+, Safari 5+, Chrome 7+
Run Test supported Browsers	Firefox 3+, IE 7+, Safari 2+, Opera 8+ Chrome doesn’t have support as of now	Firefox 2+, IE 7+, Safari 5+, Chrome 7+
Script Development	Firefox IDE + Manual coding Good API collection. But resource must be skilled in API Manual coding is more time consuming and error prone Testing of script itself is required Complex cases mostly done using manual coding	Well-designed UI that can help capture all types of scripts Codebase gets generated at background for customization if required Complex cases can also be captured with ease using UI
Supported OS	Windows, OS X, Linux, Solaris	Windows
Browser Objects Recognition	Good object recognition. Objects can be identified by name, ID or located by using xpath. Complex elements are not easy to capture Time consuming	Very Rich UI based object identification Easy identification  of html element, DOM member Provides easy way to identify element from hierarchical view Supports mouse action, drag and drop events Support java script events of control
Recording and Playback	Supported in Firefox	Supported in Firefox, IE, Safari, Chrome
Capture once & Run for all browsers	Supported	Supported
AJAX & jquery	Supported	Supported
Java Script Alerts / Dialog	Supported	Supported
Code Generation Language	Java, C#, Ruby, Perl, PHP	C#. Language knowledge is not mandatory. UI based application
Data Driven Testing	Supported Need to plug in custom code for reading data from store	Supports multiple data stores like flat file, in build table, database, excel etc. Easy to add / modify data in data store
Test Results Reports	Reporting is supported through the test runner and various logs, screen shots can also be captured. Default Reporting is not rich	Very Rich image based reporting. Step story board or failure step comparison with image is available
Performance Testing	Not supported	Supported in 2011 R2 getting release by end of Sep 2011. Support In-Depth details with .NET profiler for .NET application
Price	Free	$2500

Conclusion

We analysed Selenium and Test Studio for our requirement. The Test Studio provides better value if we do cost benefit analysis.

The projects that are being executed on Windows environment and if you are thinking of using open source framework like Selenium or watir for cost saving, then you should try Test Studio before final decision. Even for web sites that are developed in Java or PHP can take benefit of Test Studio as Web Testing is based on HTML and browser. 

Read More