Testing Blazor in WPF on Desktop?
Hi all, My project is evaluating whether we'll need to move from a pure WPF desktop application to a hybrid Blazor in WPF desktop application. Doing a very light amount of investigation, it looks like the desktop module won't work for our needs...do we also need the web module, or is Blazor just not supported by TestComplete right now?2Views0likes0CommentsObject Recognition different during recording on VM
Testcomplete Version : 15.65.50 Application: Desktop, .netframework, .wpf objects Environment : VM, Remote Connection, Windows OS11 I would like to know what are the various conditions when the parent (a Process) display has shell window instead of the process (.Net app), the child WPF object display as shell window instead of a .net wpf object? is it Missing additional libraries? API Calls are getting blocked? port blocked? firewall issues ? Account issues etc? I am trying to identify possible causes. We are setting up test complete on a new environment, From Local PC --> through citrix --> Remote into VM that has Testcomplete and AUT's installed. Anyone who has tried a similar setup if you have any inputs, please share. I would greatly appreciate all the help. Attached is a screenshot on how it looks right now, when recorded., Note: Outside this environment it records and works fine.13Views0likes2CommentsTestComplete can't detect elements in Microsoft WebView2 window
TestComplete is unable to detect any element for desktop application screens developed using Microsoft WebView2. It was working 5 days ago. Tested application wasn't updated. Now TestComplete can detect only a whole window(web-component using Microsoft WebView2), but cannot detect elements on this window. I got path "Aliases.WINWORD.WPFObject("HwndSource: WebView2Window", "Login").Window("Static", "", 1).Window("Chrome_WidgetWin_0", "", 1).Pane("Login - Web content").Panel("Chrome Legacy Window")" TestComplete version= 15.52.2.7 x64 License: Perpetual (Desktop, Web, Mobile) How can I capture of elements on the web-component window?Solved1.1KViews0likes10CommentsRunner.Stop(true) stops complete execution, not just the current test case
I want to use Runner Stop to skip some test cases in specific condition during the automatic testing. I am using Runner.Stop (true) in the event onStartTest. Project playback settings are continue runinng.. The test case item setting in the execution plan is on error; use the project on error property. How to solve this issue31Views0likes7CommentsHow to detect Application crush during test and skip test
The test application crashes during automated testing, causing delays as it verifies the objects and performs actions on the application. It keeps causing delays until the application is closed in test items after multiple test items, followed by the application open command The test framework is too large to effectively use the try-catch method on multiple functions. Can we detect the error? Testcomplete displays an exception code. i also want to skip test items if application is not available and if application is true26Views0likes1CommentWinForms existing name mappings broken with latest update
Hello. I have been developing automated tests for a legacy Windows Forms application. Today, I was prompted to update to 15.65.12.7, so I did. Wasn't the first time I've updated. I quickly found out that all of my tests were breaking immediately after startup. Many of my mappings use the property "WinFormsControlName" available on all WinForms objects and TestComplete could not find this property. What made it worse is that there were very few properties I could select (perhaps a dozen) so I might not even be able to uniquely identify my windows/controls. Clearly this is not acceptable. I saw a post online from many years ago with a similar problem and the solution was install the .NET Application Support extension. But I did have it installed. I uninstalled and reinstalled the latest version of TestComplete; the problem persisted. Installing the previous version of TestComplete (15.64.3.7) fixed it. Is there anything I could do to stay up to date?117Views4likes7CommentsModel dialogues in VM screen
In my testing environment, we are running tests on VMs connected via DRP. recently I started running tests unattended at after hours (night runs) using Tscon.exe as follows Disconnecting From Remote Desktop While Running Automated Tests | TestComplete Documentation (smartbear.com) the problem is, once you disconnected, screen resolution fall back to default. (1024 X 768) hence one of model dialogue buttons disappear from screen. it should be appear like below, was cut from red line. Can not be drag up since dialogue top is at screen top. I find this is also a universal problem windows - Screen resolution changes for the remote machine after safely closing the RDP session with "SupressWhenMinimzed" - Stack Overflow I cannot use third party exe's (such as qres) because of security. anybody out there got any solution? replacing RDP from VNC also will be huge effort (changing organizational norms)40Views0likes5Comments.ClickItem() not working anymore?
I've been using .ClickItem("&Tools | Code Tables | Agency") for quite a long time to click through to a certain menu item on a ribbon, but now that doesn't work. I get "unable to find the object ClickItem("&Tools | Code Tables | Agency") now after I updated.88Views0likes7CommentsRequesting info regarding C# language
Hi, as I see that in the official documentation of Test complete C# is mentioned as legacy language and encouraged to use the scripting language other than C#. So, I wanted to know is there any plan to discontinue the official support from Smart Bear towards using C# as scripting language in Test complete in anytime future? We are planning to create a desktop automation framework using C# language, can we go ahead with C# as scripting language? Thank you!27Views0likes2CommentsTestComplete and WPF
I've a .net 8 WPF project where I have the following steps to build it: Compile the app use donet publish Create an msi When I compile and run the app TestComplete recognizes my app as a WPF application and creates proper WPFObjects(control.NameProperty) that I can use for my test scripts. However when the dotnet publish command is run on my app (to create a self contained folder) Testcomplete no longer recognizes my app as being an accepted window (Windows.UI.Core.CoreWindow. So I can't even use test complete's spy to walk teh object tree. In my project if I check the * for accepted windows Spy will now walk the object tree but they are all UIAObjects not WPFObjects. Is there a way to tell TEstComplete that this truly is a WPF app?58Views0likes3Comments