I upgrade TC to 12.60 and everything is working as expected.
We recently upgraded the application I'm logging into
What got changed in the upgrade?
You can try recording a keyword test with the same steps as your test and see if TC can read it that way.
Also make sure that you don't have this section mapped twice.
Regarding what got changed in the upgrade? - I'm not a developer, I'm a QA person. But as far as I can tell, this was a major upgrade. We went from V15 to V18 and I'm guessing nearly everything changed.
Regarding re-recording the test - I've done that. That's how I know it is only recognizing this as one object. I cannot select the other objects as I'm recording.
Regarding mapping twice - I have validated this as well. It is only mapped once and still it is not recognizing the other objects.
I think I'm going to have to put in a ticket with SmartBear and see if I can get on the phone with someone who can see it in action and help me.
ScottVaughn1962 wrote:
Regarding what got changed in the upgrade? - I'm not a developer, I'm a QA person. But as far as I can tell, this was a major upgrade. We went from V15 to V18 and I'm guessing nearly everything changed.
So am I... QA, testers, software validator, test engineer, etc... I don't develop the applications that I test.... howevre, as a software tester, it's my job to know what changed... it's how I know what areas to test for regression, it's how I know what to do in the way of testing new functionality, it's how I know what test cases to write and execute...
So, I think it would be a good idea for you to go have a chat with the developers. When you open that ticket to SmartBear, they are going to want to know the same thing... what was in version 15 that was changed so radically in version 18. Did components change? Did the platform that was used for developing the software change? Did the architecture change? If so, on any of these, how? TestComplete supports certain versions of components, platforms, etc, and different architectures require different ways of preparing the application to be able to recognize controls. Once we know the details of the changes, we can make suggestions as to how to, potentially, get around those problems.
What tristaanogre said x100. And additionally, guessing at what changed is inefficient testing.
