Distributed Execution Infrastructure
Test Studio’s execution infrastructure is built to allow parallelization of test runs and to bring different test types into parity. Run tests from one test list across many execution systems in parallel, rather than running them in series on just one. Distributed is the default mode for remote or scheduled test lists. You’re able to turn it off to support specialized scenarios, but using distributed mode means you’ll get your test lists running much faster in parallel execution! Watch a one minute video on Test Studio's execution engine.
You don’t need to duplicate your tests for different browsers anymore. Record your tests and then execute them against all major browsers. Currently supported are:
- Internet Explorer (7.x, 8.x, 9.x, 10.x) +
- Firefox (4.x. 5.x) +
- Safari for Windows (5.x) +
- Chrome (14.x) +
The preferred browser selection prompts you to select your preferred browser – IE, Chrome, Firefox, Safari, as soon as you start creating your first test. You can save your choice for future use. You can also change the selection from the Browser Settings, or let Test Studio prompt you which browser you want to use every time you create a test. For ease of use, Test Studio will detect the default machine browser and pre-select it.
Browser Configuration Assistance
Test Studio can automatically configure your browsers for test recording and execution. We’ll go in and make all the configuration changes for you to make sure Test Studio works perfectly with your browsers. You can even recalibrate your browsers after installation if you need to and you can easily revert your browser to the pre-calibration state.
This handy widget allows users to pause the execution of a test at any time in order to launch the DOM Explorer, capture an image of the browser or view the execution log of the test. What’s more, now you can diagnose test failures real time. All you need to do is configure your Visual Debugger to auto-pause on failure. If a test step fails during execution, debugging options will be displayed specific to the failure.
Continuous Integration with Build Server
You can integrate any build server with your recorded tests. Whether you are using CruiseControl, TeamCity or Visual Studio’s Build Server, you can execute your recorded tests seamlessly on the server. Tests also run natively using Microsoft's command line execution tool: MsTest.exe and Test Studios built-in execution engine.
RunToHere For All Supported Browsers
Quite important for debugging failing tests, RunToHere is a feature many Test Studio users find irreplaceable. Test Studio supports RunToHere in all the supported browsers – IE, Chrome, Firefox, Safari. To make use of it, you just need to open the test steps and select RunToHere from the test explorer context menu.