PMularczyk
StaffJoined 2 years ago
User Profile
Staff
User Widgets
Contributions
Re: Firefox 140.0 ESR support?
Hey, Pawel from the TestComplete product team here 👋 Just a quick update — support for the latest Firefox versions is coming soon! We’ve had issues supporting Firefox versions above 115 for a while now. Over the past few months, we’ve been completely rewriting how Firefox support works under the hood. The good news is: the new approach is almost ready, and we plan to release it publicly this quarter. Once it’s out, we’ll update the documentation and, of course, include the details in our release notes. In current TC versions all FF versions above 115 will not work. Best regards, PawelRe: Display any System.GUID property in object explorer as the actual GUID raw value in WPF
You’re totally right, that’s how the GUID type is represented under the hood inside the Name Mapping component (which is a direct consequence of this: GUID - Win32 apps). While technically it should be possible to extend the Name Mapping component within TestComplete so that its string representation is easily accessible, maybe the following workaround would suffice for the time being? I assume the HomeItemButton is a class deriving from some kind of a Windows Forms button - for the purpose of example, let’s generalize it and call YourCustomButtonClass. Your HomeId property (of type System.GUID) will correspond to YourCustomGuidProperty property in our example. Now, if you want to locate it through a string representation of the GUID and click, you cannot use the default “Click” operation in TestComplete. Instead, please add the following script to your test (assuming python syntax): def find_button(your_custom_property_value): all_buttons = Aliases.Sample.HwndSource_MainWindow.MainWindow.FindAllChildren("ClrClassName", "YourCustomButtonClass", 200) for b in all_buttons: if b.DataContext.YourCustomGuidProperty.ToString() == your_custom_property_value: btn1 = b btn1.Click(); return Let’s call the script find_button Then, when you wish to click the desired button in the test, add “Run Script Routine” operation, specify the GUID (as a string) as the your_custom_property_value parameter. It should resemble something like this: Script will recursively look for your desired element by the string representation of the GUID. Alternatively, if the element is not a button and you want to do something different with it, you can create a variable in your TestComplete project and instead of executing Click directly in the Script, you can assign the element to a TC variable from within the script and manipulate/consult the variable in subsequent steps of the test: def find_button(your_custom_property_value): all_buttons = Aliases.Sample.HwndSource_MainWindow.MainWindow.FindAllChildren("ClrClassName", "YourCustomButtonClass", 200) for b in all_buttons: if b.DataContext.YourCustomGuidProperty.ToString() == your_custom_property_value: Project.Variables.btn1 = b return Please do not hesitate to contact us further if this does not address your issue or the explanation/example is not clear enough. Best regards, TestComplete TeamRe: Confusing version information (15.55 to 15.58)
Hey, version 15.56 unfortunately contained several bugs that caused problems for our users. Version 15.57 was functionally the same version as 15.55 (it was a rollback and the changes from 15.56 were rolled back). Version 15.58 contains all the changes that were in 15.56 but in addition some things that have been improved. Version 15.59 will be the version with more new changes and improvements. I hope I was able to make this clear. Best, Pawel form SmartBearRe: TestComplete Test Adapter (v15.53.9) issues running tests in DevOps
Hey nandini_thota please try this things: Try changing the preferred test runner here to, let's say, 32bit and back to what you had If that doesn't help, please check that the options.json (_work\1\s\TestCompleteAdapter) in the agent folder on which this is executed contains this "preferredRunner": "TE" If you have further problems, please write to our support. We will certainly be able to solve it then. Best regards, Pawel
