To learn which Chrome versions are supported by TestComplete, go to the Google Chrome Patches page. Remove or rename the \Google\Update folder. Locate or create the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update\UpdateDefault registry value (REG_DWORD) and set it to "0". Use the Google Update ADM template as described on the Google Update for Enterprise web page and set the Administrative Templates > Google > Google Update > Applications > Google Chrome > Update policy override property to "Manual updates only" or to "Updates disabled". To avoid this, we recommended that you disable the browser’s auto-update feature on the test machine and install the latest browser version that is supported by your version of TestComplete manually. If the browser auto-update feature is enabled, it can automatically upgrade Chrome to a version that is not yet supported by TestComplete. New versions of Chrome are released frequently. Right-click the shortcut and select Properties from the context menu.Īppend -disable-hang-monitor and other needed switches (separated by spaces) to the Target value. If you launch the browser manually, you can specify the needed switches in the shortcut parameters: To specify other switches, use the Browsers.Item(…).RunOptions property. When the browser is launched in any of the ways described in the Launching Browsers topic, TestComplete automatically uses the -disable-hang-monitor switch for it.
Use this argument to improve playback performance, especially for testing pages with a large number of objects. Specifies a custom folder for storing user profile data.ĭisables creating MSAA/UIA web page objects. Requires the -user-data-dir and -disable-site-isolation-trials arguments to be specified. Specify this argument to test HTML files that reside on your local computer.Įnables testing of web pages that use cross-origin framesets, for example, iframe elements that load data from a source other than the tested page’s original source. You may omit it for shorter tests.Įnables testing of local pages ( file://.) that use framesets displaying other local pages. This argument is required to run tests that work for 10 minutes or longer. However, depending on your test specifics, you may need to specify some of them to run automated tests: Command-Line Argumentĭisables the Chrome hang monitor to prevent it from considering the SmartBear Test Extension unresponsive during long test runs.
In general, none of them is required by TestComplete. Chrome has a variety of command-line arguments.
0 kommentar(er)
