artw
Occasional Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Headless test not working
We are looking into running our scripts with headless web browser. I followed the instructions on the smartbear website. https://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/headless.html My first simple test is to open a page and fill in some fields and click a button, see the code below (actual url and login details are replaced in the code below): The test code works well when we use Browsers.Item but it does not quite work with Browsers.RemoteItem for us. Once the URL is opened it fails to recognize the page elements.: I am not sure that it is supposed to say "local browser" or something else in the log. Interestingly the code above, which I assume is for headless browsers only, works if I happen to have chrome open and the url I'm testing is opened. This is as if the test still runs in a non-headless mode. The chrome version is:Version 102.0.5005.115 (Official Build) (32-bit) The webdriver under C:\ProgramData\SmartBear\WebDrivers\chrome seems to be the latest stable version: Ultimately we plan to run our scripts/keyword tests using TestExecute. Any help/guidance would be appreciated.Visualizer and source control
We recently added our test complete projects and as suggested in my other question I turned off "bind visualizer frames to SCC". I am not sure what are the best practices with regard to working with SCC. I still have two issues. Issue #1. When I try to add a new mapping and the NameMapping is not checked out the application tells me that "to perform the action I need to check out the MameMapping item". I click ok and I get an error stating that a png tile is not found in my workspace or I don't have a permission to access it. The error popup lists many different png files and a NameMapping.tcNM is also listed. I can only click OK and nothing happens. When I go back to the project explorer I can manually check out the NameMapping by right clicking and selecting check out for edit under source control. Then I get a confirmation dialog with all the png and .tcNM files listed. Once I check those files out I can add a new mapping Why doesn't the application know automatically what needs to be checked out when I simply want to add a new mapping? Do I always have to check out the NameMapping manually before I try to add a new mapping? Issue #2 Even with "bind visualizer frames to SCC" turned off I am still getting those png files checked out automatically. I am guessing that slows SCC interactions too. Should the references to them be removed and what's the best way to do that? What's the best practice to handle this? Do I need to have "collect test visualizer data" options set to off even when the "bind visualizer to scc" is not checked?
