You can use browser aliases or paths to executable files to specify locally installed browsers. Related configuration file property: browsers. The browser-list-comma-separated argument specifies the comma-separated list of browsers where to run tests. If the same problem occurs with this test two more times, the test run finishes and TestCafe throws an error. If a browser stops responding during test execution, TestCafe restarts the browser and reruns the current test in a new browser instance.
#REACT IDLE TIMER TIMEOUT FOR MOZILLA FIREFOX HOW TO#
For more information on how to handle native dialogs, refer to the following topic: Handle Native Dialogs. TestCafe suppresses native dialogs during a test, so that they do not block the page.
Tests may be unstable if the page is zoomed in or out. Inactive tabs and minimized browser windows switch to a lower resource consumption mode where tests do not always execute correctly.ĭo not zoom pages while testing. The browser tab that runs tests should remain active. If you specify the browsers and src properties in the configuration file, you can omit them in the command line. TestCafe prints information about every overridden property in the console. Note that command-line settings override conflicting values in the configuration file. When you execute the testcafe command, TestCafe first reads settings from a configuration file if this file exists, and then applies the settings from the command line.
0 kommentar(er)
