Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved TestComplete & Powerbuilder

  1. Advice
0
Votes
Undo
  1. Dave Russell
    Dave Russell
  2. PowerBuilder
  3. Friday, 21 October 2022 16:42 PM UTC

Hi,

Just wondering anyone uses TestComplete to run automated tests for testing their Powerbuilder software? We have been using Smartbears product called TestComplete for almost 8 years. We recently migrated to PB 2022 not TestComplete won't recognize the datawindows causing issues for the 1000's of test scripts created over the years.

Anyone have any suggestions?

Thanks

Dave 

Powerbuilder and SQL Server Multiple Plans
Windows Notification
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 21 October 2022 17:19 PM UTC
  2. PowerBuilder
  3. # 1

Hi Dave;

  The TestComplete software vendor did have issues with PB2019 and needed to address this in their v14.x releases. So I suspect that they might now have some new ones with PB2022. Please contact the SB support team for further help on this issue.

FYI: https://community.smartbear.com/t5/TestComplete-Questions/PowerBuilder-2019-classic-MSAA-TC-14-30-cannot-resolve-objects/m-p/194559

https://community.appeon.com/index.php/qna/q-a/smartbear-testing

https://community.appeon.com/index.php/qna/q-a/pb2019-msaa

Regards ... Chris

Comment
There are no comments made yet.
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Friday, 21 October 2022 17:47 PM UTC
  2. PowerBuilder
  3. # 2

Hi Dave,

eventually you see some impact by this "silent" PB 2022 feature change:

https://docs.appeon.com/pb2022/troubleshooting_guide/tr_134.html

For Help:

https://community.appeon.com/index.php/qna/q-a/pbdatawindow-objects-not-exposed-to-be-used-by-automation-tool-uft

regards

Arnd

Comment
Jeff Martin
  1. Jeff Martin
  2. Monday, 24 October 2022 10:41 AM UTC
This fixed it for us. Our implementation of Test Complete requires accessibility to be ON. So we now need to specify the below in our pb.ini file:



[Data Window]

ACCESSIBILITY=1



https://docs.appeon.com/pb2022/troubleshooting_guide/tr_134.html
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 21 October 2022 19:21 PM UTC
  2. PowerBuilder
  3. # 3

If you turn on accessibility it should work.  I would first try setting it to "2" and then if that doesn't work try "1".  Please refer to instructions: https://docs.appeon.com/pb2022/application_techniques/Creating.html

Comment
There are no comments made yet.
Dave Russell
Dave Russell Accepted Answer Pending Moderation
  1. Friday, 21 October 2022 22:47 PM UTC
  2. PowerBuilder
  3. # 4

Thanks...the ini file was change and all works great again!

 

 

  • Accessibility=0: Disable both MSAA and Microsoft UI Automation

  • Accessibility=1: Enable both

  • Accessibility=2: Enable Microsoft UI Automation only

  • Accessibility=3: Enable MSAA only

For example,

[Data Window]
ACCESSIBILITY=1
Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 21 October 2022 23:14 PM UTC
Hi,

That's great! Please mark as resolved.
  1. Helpful
John Fauss
  1. John Fauss
  2. Saturday, 22 October 2022 00:50 AM UTC
Dave, unless your users require the Accessibility feature, make sure Accessibility is disabled when you deploy the application so as not to adversely affect app performance.
  1. Helpful 1
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.