Overview
- For QA Testers
- For Developers
- For Team Leads
- Test Studio vs. Framework
- Test Studio vs. Run-Time
Installation
- System Requirements
- Install Procedure
- Activating your License
- Manual Activation
- Check for Updates
- Configure Windows Server
- Manual download
Configure your Browser
- Internet Explorer
- Firefox
- Safari
- Chrome
Create a Test (Standalone)
- Web Test
- WPF Test
- Silverlight Out-of-Browser
- Manual Test
  - Excel Import
Create a Test (VS plugin)
- Web Test
- WPF Test
- Silverlight Out-of-Browser
Test Recording
- Recording Toolbar
- Frames
- Translators
Test Execution
- Quick Execution
- Visual Debugger
- Test Lists (Standalone)
- Test List Type (Standalone)
- Visual Studio 2012 Test View
- Visual Studio Test List
- Test List Settings
- Visual Studio 2012 Test Explorer
Test Results
- Step Failure Details
- Quick Execute Test as Step
- Calendar
- Analyze Test Results
- Export Test Results
- Reports
- Test Results (VS plugin)
Test Maintenance
- Steps Pane
- Reorder Test Steps
- Search Test Steps
- Test Step Properties
- Test Step Context Menu
- Test Properties (Standalone)
- Test Properties (VS plugin)
- Project Files Context Menu
- Search Tests
- Storyboard
- Export to Visual Studio
- Change Step Target Element
Dialogs & Popups
- Dialogs
- HTML Popups
- Modal Popups
Elements Menu
- Common Tasks
- 3D Viewer
- DOM Explorer
Verifications
- Quick Verification
- Advanced Verification
- Wait
- Extraction
- Freeze Mode
- Image Verification
Elements Explorer
- Find Element
- Step Suggestions
Exploratory Testing
- Launch Tool
- Provide Feedback
Manual Testing
- Start a Manual Test
- Fast Forward Test
- Import and Export Excel workbooks
- Convert to Automated
Data Driven Testing
- Local Data Driven Test
- Add a Data Source
  - SQL Database Example
- Bind a Test to a Data Source
- Attach Columns to Input Values
- Attach Columns to Verifications
- Multi-Level Tests
- Quick Execute Results
- Test List Results
Custom Steps
- Test as Step
  - Create Test as Step
- Script Step
- Comment
- Capture
- Execution Delay
- Custom Annotation
- Clear Cookies
- Wait For URL
- Inspection Point
- Manual Step
- Change Window State
Logical Steps
- If...Else
- While...Loop
- Loop
Coded Steps
- Code-Behind File
- Preview Code
- Convert All Steps to Code
- Reference an Element in Code
- Add an Assembly Reference
Code Samples
- General
- HTML
- Silverlight
- WPF
Performance Testing
- Gather Performance Data
- History View
- Overview
- Details View
- Compare View
- Open Port on Server
- Export Results
Load Testing
- Installation
  - Add Controller & Reporter
  - Add Load Agent
- Configuring Services
- Designing Tests
- Running Tests
- Analyzing Results
- Troubleshooting Results Errors
- Managing Virtual Users
- Best Practices
- Known Issues
- Generating Reports from SQL
Scheduling Test Runs
- Create a Scheduling Server
- Create an Execution Server
- Connect to Scheduling Server
- Run List Remotely
- Schedule Execution
- Scheduling Results
Source Control
- Connect Project to TFS
- Open TFS-Controlled Project
- Project Item Options
- Source Control Alternatives
- Check-in Guidelines
Extensions
- TeamPulse
- Quality Center
  - Connectivity Instructions
  - Integration
- Bug Tracking
Project Settings
- General
- Highlighting
- Recording Options
- Identification Logic
- Script Options
- Translators
- Installation
- Browsers
- Extensions
Build Server Test Execution
- MSTest
- ArtOfTest.Runner
- Continuous Integration
- ManualRunner
Troubleshooting Guide
- Troubleshooting Tools
- Browser Inconsistencies
- Installation Problems
- Cannot Launch Test Studio
  - Package Load Failure
  - Reset Skipped Packages
- Recording Problems
- Test Execution Problems
- Verification Problems
  - Works in IE, not Firefox
- Visual Studio
- Load Testing Problems
  - Cannot Connect to Reporter: 'DbProviderFactories' error
Knowledge Base
- Activation
  - Swap License
- Best Practices
- Code Coverage
  - Using NCover
  - NCover Execution
- Data Driven Testing
- Dialogs/Pop-ups
- Project Configuration
- Scheduling
- Silverlight
- Test Automation
- Test Execution
- Verification
- Visual Studio
  - Convert .trx to HTML
  - ReSharper Compatibility
Testing Framework: Getting Started
- Using the Framework
- Automate Browser Actions
- Using VS Team Test
- Using NUnit
- Using xUnit
- Using MbUnit
- Frequently Asked Questions
Write Tests in Code
- Intermediate Topics
- Advanced Topics
- Silverlight / WPF Automation
API Reference
Release History
Test Studio Backward Compatibility
API Changes & Backward Compatibility
Release Guide
- R2 2012 SP1

Create an Execution Server

The Execution Server is an instance of Test Studio Standalone, VS plugin, or Run-Time Edition. 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.

Several Execution Servers (ES) can connect to the same Scheduling Server (SS). Multiple Execution Servers allow you to execute multiple test lists simultaneously. Physical and virtual 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. Ensure there are no Test Studio version differences, however. 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 off.
Ensure the location of your test project is accessible from the ES.

You may need to change the account under which the Scheduling service is running. The default is to use the Local System Account. Often this account does not have permissions to access external file shares.
Load the Services Console, locate Telerik TestStudio Scheduling Service, right click it and select Properties, and go to the Log On tab.

Configure the Execution Server

After successfully installing Test Studio, run the Execution server software:

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

Version 2012.1.528 & older
R1 2012 SP2 & newer
Click Register/Connect.
Add the Server name and port for the machine on which your SS is running. The default port is 8009. A Connection URL is generated from the server name and port number. If the Execution Server and Scheduling Server are not on the same domain, use the IP address for the Scheduling Server instead of the machine name. Change the URL if you previously edited the default URL when configuring the SS.
Edit the test execution folder if desired. This should not match the Project Source Location set when you Connect a Project to the Scheduling Server.
Click Register/Connect.
You should see a message that states The machine has been successfully registered for scheduling test runs. Click OK.
The Telerik Test Studio Execution Server application opens. Do not close this application; it is required to be open for your tests to execute. Click the X in the upper right of the window to minimize it to the system tray.

Version 2012.1.528 & older

Version 2012.1.719 & newer