Forum

For recording test scripts of our software we use a product called Test Complete from Automated QA (http://www.automatedqa.com/).
I’ve noticed that since switching to a Prof-UI interface recorded interactions no longer return names for menu items - I just get click locations instead.
These fail where the menu item I’m aiming for is part of a submenu triggered by a mouse over on the second menu item.

For example, one test might be accessing Settings > Toolbars and Windows > Colors.

Before the new UI steps would get captured as:
w.MainMenu.Click("Settings|Toolbars and Windows|Colors")

With the new Prof-UI I get:
w.Window("ProfUIS-ControlBar", "Menu Bar").Click(499, 13)
// this is the ’Settings’ click.

p.Window("Afx:00400000:800*", "", 2).Click(64, 15)
// this is the ’Colors and Pen’ click
// which fails because ’Toolbars and Windows’ doesn’t get activated.

Any ideas as to how I could avoid this problem would be much appreciated.

how to convert pdf document into html document in using ASP.NET??

tryy

I’ve created a small test project to work with your sample application - DRAWCLI-m.exe.
Where should I send the zip file containing the Test Complete project? I don’t see a way to attach it to my post here.

Please send it to support@prof-uis.com.

Thanks for the reply - I’m interested in hearing how you get on with implementing compatibility with Test Complete.

Would it be possible if you could create some small Prof-UIS project and Test Complete project which testes that application so we can look into how the Test Complete works and add needed changes to Prof-UIS? We mean a test project that shows the problem.

Prof-UIS menus are not based on the Windows menus. They have much more features and do not compatible with HMENU windows. Prof-UIS menu items are based on CExtCmdItem command description objects stored in the CExtCmdProfile command profile in the CExtCmdManager command manager (accessed with the g_CmdManager global smart pointer variable). This design allows Prof-UIS menus and toolbars to automatically share command parameters between different interface objects. So this technique makes Prof-UIS menus inaccessible from third party applicationslike Test Complete from Automated QA.

Of course we can provide compatibility with Test Complete but we need your assistance with this. For instance you may want to create some small Prof-UIS project and Test Complete project which testes the Prof-UIS application. We will install Test Complete and look into how it works so we can add needed changes in the Prof-UIS code.