Set web slider position without dragging slider
Hi guys, Is there a way to set the web slider position, without the need to drag the slider (or using cursor/page up/down keys)? I found SetPosition action or wPosition property, but neither seem work with the web objects. And yes, I also tried set "Keys" or "value", but these does not work either. Thanks for any idea :) PS: I ended-up with below solution, using Keys action. else if (inputElement.ObjectType == "Slider") { inputElement.Keys("[Home]"); for (let i = 0; i < (csvInputValue/10); i++) { inputElement.Keys("[Right]"); } } Basically, it Home key sets the slider to zero position and then Right key in loop sets the slider to expected position.
Multi-View Electron app
I'm trying to recod tests on an electron app that is made from two "pages" side by side. I couldn't detect the objects, i had to check that "*" in the MAAS settings. Now when I spy the page on the left, it's pointing the file of the page on the right, and the screenshot in the object browser displays the right page instead of the left page. The lest page's screen shot is correct though. So basically, it's as if TestComplete was unable to take in to the accound the position of the right view. The other major problem is that when i click on the app, the actions aren't being recorded.
How to setup Edge TestComplete Extension settings in script?
I am running tests from Azure Pipeline. This pipeline is preparing required Win11 Virtual Machines and then it starts Test Plans using Test Execute. Several test plans requires to open local html files, but this can be done only if in TC Extension we enable "Allow access to file URLs". I have created test case which is enabling this option, but unfortunately this works only when I run Test plan manually in TestComplete. When I use Azure Pipeline to start this full testing, it is always failing in very beginning to find Details button inside Installed extensions page. First, in order to see Edge Settings page Objects I have enabled to accept any window in Current Project Properties(Found this suggestion in this forum) And only then I was able to see all objects from Edge settings page in Object Browser, but Object Spy still does not recognize any object and shows only the main page info. In test itself, I am opening extensions webpage and checking if its Object Type is Form. This way I hope that all mapped objects of this Form will be initialized. Then I am setting a variable with direct path till this Details button and it worked, but only on manual test, failed in Azure pipeline. Then I have mapped this Details button and all its parental objects. Used this Mapped Objects path and it worked on manual run, but again failing when i run same test in Azure Pipeline. Variables for this button If condition to check if this button is visible on each variable. On Manual run I am getting success when in azure Pipeline with new fresh VM it failed reported error about failing to find button Details object property I have made many tests and various additional actions to refresh Object browser, refresh mapping, added various delays and checks, but nothing is helping and each time it fails on Azure pipeline. The difference is that in Azure Pipeline it is always creating new virtual machines, installing all required software and then starting Test plans. So each time it is new fresh test environment and new first start for Test Execute. I assume this new fresh start is the cause of it and it fails because everything is empty. Any suggestion how I could get those Edge extensions page objects initialized in very start of testing? It seems that those, somehow are not active or does not exist and then mapping does not work. Thank you all in advance.
Warning messages in the test run log for improve performance
Hello, Recently I have updated all my nameMapping to use unique identifiers in the XPath and deleted all others that TC saved when recorded. So tipically I have only one selector for each object or element. When I ran the test it gave me the following warning almost for all the objects. You can improve the performance of the object search in the test. The NameMapping.Sys.browser.pageAuth.login_SignIn_Btn object can be found faster if you make //input[@type="submit"] the first selector in its selector list. And in the nameMapping for this object I see only one selector as I mentioned above. Still not sure why its throwing warning messages. Even when I click on Improve performance button in the log it just added an Empty selector, and even with that when I rerun the test it gave same message. One another thing is that the Extended Find column doesn't have any checkboxes. Is there something I missed in the settings or somewhere else TIA
Edge browser compatibility
Hi all, with latest Test Complete and Test Execute version (15.63) we are experiencing lot of issues with the Edge browser interaction, for our web tests. For example, the following errors and exceptions makes not possible to correctly execute the tests: Unable to navigate exceptions: Other strange exceptions when launching Edge: We have found this page: https://support.smartbear.com/testcomplete/docs/app-testing/web/general/supported-browsers-and-technologies.html , where it is listed that the supported browser version is: Microsoft Edge 83 - 121 (Chromium-based, both 32-bit and 64-bit versions) Since the 121 version is a very old one (released on December by Microsoft), Test Complete is really not supporting any new versions of this browser? Or is this page hopefully containing obsolete information? Currently we have got the version 123, since the browser is updated automatically by O.S. and Edge browser cannot be downgraded. Could you please let us know if latest versions are really not supported? Regards, SimonaSwitching between headless/non-headless execution
Is there a good way to do what the title says? I have a switch statement that will launch my browser and login either headless or non-headless: function chooseTestMode(mode) { switch (mode) { case "non-headless": runNonHeadless(); break; case "headless": runHeadless(); break; default: runNonHeadless(); } } This works but the tests that I actually want to run either headless or non-headless, may have navigate statements or other actions which will not for both test modes. What is a good way to handle this? Is there one?
