Standalone version: On the Test List tab, highlight a test list and click the Edit Settings button in the Edit ribbon.
VS plugin: Double click Local.testsettings under Solution Items in the Solution Explorer.
To create a Test Settings file in Visual Studio, right click Solution Items and select Add > New Item. Click Test Settings under Installed Templates, customize the name if desired, then click Add.
This opens a dialog box that shows all of the possible configuration settings for that test list. Change the settings as needed for your test list.
- AnnotateExecution - whether to highlight and annotate the target element that the current action is being executed against.
- AnnotationMode - the annotation mode when annotation is enabled.
- ClientReadyTimeout - the timeout, in msec., to wait for a client to be ready after initial launch and after executing a command.
- DisableDialogMonitoring - whether to disable handling of dialog windows.
- ElementWaitTimeout - the global wait on elements timeout used during execution. Default is 10 seconds.
- ExecuteCommandTimeout - the timeout, in msec., to wait for a command request to execute.
- ExecutionDelay - the length of execution delay, in msec., to insert between commands. Note: Some test steps represent multiple commands.
- UnexpectedDialogAction - specifies the action that the DialogMonitor should take when it encounters unexpected dialogs.
- WaitCheckInterval - the wait interval, in msec., to use between checks for all the Wait.For methods.
- XMultiMgr - whether to use WebAii 1.1 style connections.
- CreateLogFile - whether to create a log file on disk.
- LogAnnotations - whether to log annotations to the log file.
- LogLocation - the location where to perform the logging.
- QueryEventLogErrorsOnExit - whether to query the event log on manager exit for any error logged from automation clients.
- AspNetDevServerPort - the ASP.NET development server port to use, if enabled. If set to -1, a random port is generated each time the manager is created.
- LocalWebServer - the local web server to use. When set to AspNetDevelopmentServer, the ASP.NET development server is started.
- WebAppPhysicalPath - the path to the application to test when running under the ASP.NET development server.
- Browser - the default browser to launch.
- EnableUILessRequestViewing - whether to allow debugging of UILess page requests using a UI browser, like IE.
- KillBrowserProcessOnClose - whether to kill the browser process when closing the browser.
- RecycleBrowser - when set to true, one instance of the browser is launched and recycled throughout all tests until Manager.Dispose is called.
- UseHttpProxy - whether to use the built-in HTTP proxy during automation. Enabling Silverlight will automatically enable the HTTP proxy.
- EnableScriptLogging - whether to enable script logging.
- VerboseHttpProxy - whether the HTTP proxy produces a high level of tracing output.
- ExecutingBrowsers - Select the browsers against which you will execute the test list. Supported in Test Studio Standalone version only.
- BaseUrl - The BaseURL to use for all NavigateTo commands. When set, NavigateTo steps should use a relative URL (i.e. "~/default.aspx").
- EnableSilverlight - whether to enable Silverlight automation. Enabling Silverlight will automatically enable the HTTP proxy.
- SilverlightApplicationPath - the web address or local directory from which to load a Silverlight application.
- SilverlightConnectTimeout - the amount of time to wait for a Silverlight application to load before timing out.
- DefaultApplicationPath - represents the default application path for WPF tests.
If your Visual Studio Test List runs for more than 30 minutes and fails with an *Execution Timeout Exceeded** error, change the following setting:*