Contributions
TestComplete launches 32-bit cmd.exe (i.e. cmd.exe*32 process)
We need to invoke a test application via command prompt. The application is a 64-bit app and NOT supported on 32-bit. What I need? 1. Invoke Command prompt from TestComplete (using VBScript). Windows 7 64-bit is being used. 2. Run application using command line arguments 3. Further processing.... Where I'm stuck? Unable to launch "cmd.exe" using TestComplete. Using any of approaches below "cmd.exe*32" process is launched. When we run our application "32-bit Windows not supported" is shown (which is probably a custom application message) Approaches (all of them launch cmd.exe*32) 1. Add cmd.exe to TestedApps (more specifically C:\Window\system32\cmd.exe) and then using TestApps.cmd.Run(1, True) 2.Using WScript: Set oWShell = CreateObject("WScript.Shell") oWShell.Run("cmd") Note: When launching command prompt manually via Windows > Run > cmd, cmd.exe is launched. It seems really silly to me, so coming straight off to the forum for urgent help.1.7KViews0likes1CommentRe: Member Not Found error when trying to set Value for a MSAA control
Allen, thanks for all your answers. I found that there is a DLL - PBACC100/105 which if registered in the host machine helps counter the error. Installing powerbuilder helped identify objects in more depth. Thanks again. V877Views0likes0CommentsMember Not Found error when trying to set Value for a MSAA control
I am using TestComplete 7.1 and trying to automate a Powerbuilder application. A lot of issues with setting values for the control are cropping up with both the New Mode using MSAA engine as well as the Compatibility mode using MSAAObjects. New Mode 1. When using this, I am unable to set value for Edit controls(using "Text" property). TestComplete throws "Member Not Found" error when trying to do so. 2. For DropDown controls I am unable to find any property/method to set value in the control. Compatibility Mode Again the "Member Not Found" error is thrown when using "Value" property to set the value for controls with role = "editable text" or role = "drop down" This is very urgent. Can you please help me out. Thanks, V14KViews0likes2CommentsRe: Automating Powerbuilder apps
Thanks. I did go through that Help section, and it was of some help. But I still have a few questions: 1. Is only pbdw (Powebuilder Datawindow) object only to be added to the MSAA list of accepted windows and none other such as FNWNS or FNWND windows that TestComplete identifies for Powerbuilder apps. 2. I am unable to interact with couple of controls such as DropDown - no property could be found to set value for a DropDown 3. TestComplete throws a "Match not found" error when trying to set value for "Text" property of Edit control. 4. Is Powerbulider needed to be installed on the machine being used for automation, since I suspect couple of dlls and library files are missing. I get the attached error sometimes - PowerBuilderAccessiblityError.jpg Vaibhav3.4KViews0likes0CommentsAutomating Powerbuilder apps
Hi, I need to automate a legacy application developed using Powerbuilder 10.5 using TestComplete. However I am unable to identify the proper object model. I automated a WPF app just before this and for the correct object model to be identified in TestComplete Object Browser I had to add a few .NET GAC assemblies as well as a custom control class used in the application. Is there a similar setting required for Powerbuilder as well? Many thanks for any help you can provide. Vaibhav25KViews0likes7Comments