Don't update Chome to v140
For those of you that didn't follow this ticket: Chrome minimizes and reopens every on screen action | SmartBear Community When Chome v139 came out TC stopped working with Chome (and edge). This was fixed in TC v15.77.6. Now Chrome updated again to v140, Testcomplete v15.77.6 does not work with Chome again. If you updated Chome already i recommend downgrading Chrome back to v138 or v139.
TC\TE - ObjectSpy issue with latest MS Edge 138.0.3351.121
Just checking to see if others experience this issue. For the most part, the rest of the products I automate and their frameworks do not have this issue. I have one product, that does not change that must from developer changes. It has always worked until a few months back when ... Scripts that worked previously are failing due to TC\TE unable to penetrate the webpage to find the web elements as usual. Scripts can log into the application, but from there ... ObjectSpy can only outline the outer boundary. Manually going into Object Browser with the web page open, I can see and go the the page objects (highlight on screen) that the test script should be finding when running the script. But since not able to penetrate the web page and ObjectSpy red line outlines the outer panel, the value I am trying to enter into a text box jumps up to the MS Edge URL section. I have uninstalled/re-installed the latest TC\TE to verify issue still exists. TestExecute extention is in the Edge browser. I know MS Edge updated around this time period. This is issue is not encountered with Chrome, just MS Edge ? I had opened an IT ticket for this and worked with support, but no solution came from it. I am thinking of switching to using Chrome instead of MS Edge, but this issue bugs me for why it stopped working. I continue to try different things from day to day. This issue has killed my automation for this product. Suggestions? Has this issue been reported from others, and work-around or patches available?Checking API Status in TestComplete
Introduction I first saw the need to verify the state of an API several years ago with an application that used an address validation API in several of it's operations. If this API was down or did not respond in a timely manor, many of the automated test cases would run and fail. In this case, and in others, I have found that doing a simple call to the API to check the returned status code allowed me to skip, fail or log a warning with a logical message instead of allowing the application to fail with another less direct error message due to the API issue. The aqHttp Object The TestComplete aqHttp object and it's methods are very useful for performing simple checks like this and are also useful for other more complex tasks like leveraging an API to return a test data set or even verifying a certain data is returned prior to running tests against the UI that depend on the data. Sending and Receiving HTTP Requests From Script Tests More Complete API Testing Most proper API testing should be done using a tools like ReadyAPI or SoapUI. Both of these tools will integrate with TestComplete or can be used alone and will provide much more capabilities and automation options. Integration With ReadyAPI and SoapUI Code Example Here I have provided a working example of how to code a Get request using 'aqHttp.CreateRequest' to confirm an API returns a status code of 200 and it will log the returned records. function sendGetRequest() { let resourcePath ="https://restcountries.com/v3.1/all" let resourceQuery = "?fields=name,capital"; let url = resourcePath + resourceQuery; try { // Send GET request let response = aqHttp.CreateRequest("GET", url, false).Send(); // Check for successful response if (response.StatusCode === 200) { // Parse JSON response let allData = JSON.parse(response.Text); Log.Message("Total records received: " + allData.length); // Process each record allData.forEach((record, index) => { Log.Message("Record " + (index + 1) + ": " + JSON.stringify(record)); }); return true; // Send a bool back to the calling function. } else { throw new Error("Failed to fetch data. Status code: " + response.StatusCode); } } catch (error) { Log.Error("Error during request or data processing: " + error.message); } } Enhancements You could accept parameters for the resourcePath and resourceQuery. Parameterize the logging loop run or remove it. Return the JSON to the calling function for use. Perform other tasks based on the return code. Conclusion With the growing use of API calls in desktop applications and the fact that APIs are almost the foundation of any web site checking an API before a test case run is almost a requirement for consistent test runs and good error logging. This small script can bring big rewards to your test runs and reports. Cheers! I hope you find it as useful as I have! If you find my posts helpful drop me a like! 👍 Leave a comment if you want to contribute or have a better solution or an improvement. 😎 Have a great day
Clicking on Button while page is still scrolling
TestComplete is trying to click on web page buttons while the screen is still scrolling the object into view. This is causing scripts to fail as it's either now clicking the wrong button or clicking where the button used to be but no longer is. If I put a hover before the click it fixes the issue, but that will be a lot of extra steps in every script to hover before clicking any button. Is there a delay I can set to have it not click the button while still scrolling into view?
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, Simona
