Basic actions taking significantly longer when run as part of ADO pipeline
Our nightly CI/CD ADO pipeline runs tests on a dedicated VM solely for running these tests. We have ~140 tests which run over a period of 6-7 hours. When we execute tests as part of the release pipeline via ADO, the tests take on average 20% longer than they do when they are run manually via TestExecute on the exact same machine. Regardless of whether we run just 1 or all ~140 tests through the pipeline, the result is the same. The tests are executed using the tscon disconnection method to run headless, and the same script is run before the comparisons so it isn't related to that. Investigating further into the details, the execution time difference seems to come from extremely basic actions. An action that would take 1 second, can often take 15 seconds when the test is run as part of the pipeline. Some examples of these actions are: A click with no key pressed. Tested object: Aliases.Application.MainForm.buttonMenu.wItems.Item["Browse"].Items.Item["Search"] (Sys.Process("Application").WinFormsObject("MainForm").WinFormsObject("buttonMenu").wItems.Item["Browse"].Items.Item["Search"]) A click at point (10, 10) with no key pressed. '^[F4]' was sent as a keyboard input to the following window or control. Selecting values in combo boxes takes up to 7 seconds. Even just giving focus to Edge takes 10 seconds: 'The window got focus' -Tested object: Aliases.browser.BrowserWindow (Sys.Browser("edge").BrowserWindow(0)) I've tried searching the community for similar threads but have had no luck. Any suggestions or help would be greatly appreciated.
Button is recognized but is not clickable.
Hello everyone. I need your help to figure out why the button on my mobile app (Android) is not clicked even though TestComplete recognizes it. The code is very simple: if completeButton.Exists: Log.Message("The button exists") completeButton.Click() It returns "The button exists". However, the button is not clicked. I suspect that the issue is because the button is partly covered with home icon as the image shows. Please tell me your thought and advice to fix this error. Cheers.Cannot Open Sys Object Tree
Hello! I'm using testComplete for my application testing. In the object browser, Mobile and Sys are listed. I can open the Mobile object tree but cannot open the Sys object tree. More detail: I’m not able to get sys object tree, when I go with Object Spy > Highlight object in the object tree I receive message "cannot highlight this object in the object tree" but this object exists on the screen and when I use function 'Highlight object on the screen' it is highlighted. It happens to each object I tried (WPFobject such as buttons, cells). What I did: I updated the latest version of TestComplete(v 15.73.16), then sys object tree appeared. However, as I opened my file and start working, the object tree was not opened. Please give me any advice to solve this problem.
Name Mapping not working on remote browser
The name mapping and test cases work fine on local browsers, but would complain about page or object not found when running headless remote browsers and in parallel testing. I have the following setup for browser name mapping: For headless setup I have: server = "localhost" capabilities = { "browserName": "chrome", "headless" : "true", "screenResolution": "1920x1080", "platform" : "Headless", "record_video": "true" } Browsers.RemoteItem[server, capabilities].Run(url) Is this the correct way to work with name mapping on headless browser?Azure Pipelines - Runs on TestComplete instead of TestExecute
Hi all, So it seems like my UI tests are running with TestComplete instead of TestExecute and im trying to figure out why. In my pipeline i do request to use/prefer TestExecute: But for some reason it will run them with TestComplete and therefore consume a license which are supposed to be dedicated to my testers. So 5 TC licenses and 7 TE licenses and 6 agents running UI tests at night. Since they seem to run TC many pipeline are failing since they cannot acquire a license. I guess my next solution would be to install only TE on the agent's machines but i like to have TC there for debugging purposes. It was working just fine a few weeks ago... What could be causing this issue?
