When you run your tests in BitBar environments, the test results are copied to your local computer and are accumulated in a single log automatically. You do not need to distribute your test projects to remote environments and gather test results from them manually. BitBar environments are already prepared for running tests. You do not prepare your testing environments manually. In addition, you can set the screen resolution for your testing environment if you need to. You can test your web application in any web browser and on any operating system that BitBar provides. This can be a good solution if you need to run tests in various web browsers without actually buying additional software and hardware: To learn how to do it, see About Cross-Platform Web Tests. Starting from TestComplete version 14.40, you can create cross-platform web tests and run them in all environments that BitBar provides (including headless environments and those that are not supported by TestComplete directly, like Mac OS). In addition, you will have to copy your test projects, run them and gather test results on those computers manually or use third-party QA management tools to do that.įor information on how you can automate your test environment management, see the section below.īitBar is a cloud service that provides virtual environments for running functional web tests. If you run tests on remote computers, you also have to prepare those remote computers and web browsers on them manually. You have to manage environments where you run tests manually.įor instance, if you run tests on your local computer, you need to make sure that correct versions of all needed web browsers are installed on your computer and prepared for testing. For information on handling browser specifics, see Handling Browser Differences. Another example is special dialogs that some browsers display in certain cases. Though TestComplete web testing features are cross-browser, there still can be specific cases that require your attention and special handling.įor instance, actions on most of the browser’s GUI elements (menus, toolbars, tabs, and so on) are browser-dependent and should not be used in cross-browser tests. For complete information on these, see Handling JavaScript Popups and Browser Dialogs. This means your tests work with these dialogs and message boxes in a unified manner, using the same API that does not depend on the web browser you use for testing. TestComplete supports commonly used modal dialogs, like JavaScript alerts, prompts and confirmations, standard authentication dialogs and others. Handling them is typically a challenging task as different browsers use different GUI implementation for them. Web pages can display various messages and dialogs. Support for JavaScript messages and browser dialogs. TestComplete offers a synthetic property - contentText - which is available in tests for all supported browsers and lets you create your tests in a browser-independent manner. For instance, in Firefox and Chrome you use the textContent property, while in Internet Explorer and Edge you have to use the innerText property. See Accessing DOM document Object.ĭifferent browsers use different properties to return the textual contents of web page elements. In TestComplete, you use the Page(.).contentDocument property that provides access to that object regardless of the browser used. Unified access to the document object and elements’ data.ĭifferent browsers use different properties to return the page’s document object. To obtain information about the current browser in scripts, you can also use the CurrentBrowser property of the Browsers object. Moreover, when referring to a web page that is not displayed in the current browser, TestComplete may automatically switch to the browser instance that contains the specified page and make this browser the current one. After you use TestComplete keyword-test operations or script methods to launch a browser or open a web page, the Aliases.browser item refers to the current test browser, that is, to the browser that was specified by the operation’s or the method’s parameter. The default mapping settings for the Browser processes use only the process type (“Browser”), but not the actual browser name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |