Solved
Namemapping nightmare
Hi, I am new to Testcomplete and having trouble with namemapping. I am using Testcomplete to test a WPF based application. The issue is that UI on the application keeps changing, and each time ...
Forum Discussion
If I am understanding you correctly, the development team is making changes to the UI that changes your mapping such that the tests you've written no longer work.
I had the same issue and asked dev to find a property on each form that is decriptive in nature and not being used. I had them put a unique 'name' in this property (frmLogin, scrnEntry) and used this plus a FEW other properties that will not change to map the screen.
As you have noted the closer the form/screen is to the root of the app, the more critical it is that this property is maintained as poorly executed changes here definitely screw up the mapping.
I also asked dev to ensure that if a control on a screen is deleted, replaced, or modified that the unique property carry the same name as the one used for mapping.
The company spends good money for TC and your paycheck, dev can help you and the company maximize the return on this money by doing this. Good luck!
Jon
I had the same issue and asked dev to find a property on each form that is decriptive in nature and not being used. I had them put a unique 'name' in this property (frmLogin, scrnEntry) and used this plus a FEW other properties that will not change to map the screen.
As you have noted the closer the form/screen is to the root of the app, the more critical it is that this property is maintained as poorly executed changes here definitely screw up the mapping.
I also asked dev to ensure that if a control on a screen is deleted, replaced, or modified that the unique property carry the same name as the one used for mapping.
The company spends good money for TC and your paycheck, dev can help you and the company maximize the return on this money by doing this. Good luck!
Jon