05-19-2017 06:37 AM
Sorry Tom, I can't do further since I don't have access to your web page and also we don't web module license.
Certain things i can answer which by looking at your properties and how you can map and all, In this case time needs to be spend on understanding all properties and difference between each parents and all.
“You must expect great things from you, before you can do them”
05-19-2017 06:59 AM
Just want to verify something... the problem we're trying to figure out is why the same page is showing up in your namemapping twice. Is this correct?
If so, based upon the mapping criteria you have shown with the properties, etc... they are the same page... so, there are two explanations I can give for this.
1) Someone deliberately mapped the same page twice, possibly unknowingly. In my current employment, this has happened where two people are working on similar automation work and are not aware of what the other person is doing. So, they end up mapping the same item twice but with different names. The name that you are seeing (pageAssuranceSimplified and pageRedFlareSimplifyingAssurance) is something that someone entered when they were doing the mapping.
2) If you were recording a test case, there was some sort of situation where TestComplete did not recognize that the page had already been mapped. Perhaps the page title was different in your development. Perhaps there is some other criteria on the page that is different. In any case, the initial recognition determined that it was a different page than what was mapped.
Delete one. :-) If you don't need to have both pages, then you can easily delete one. Now, this may be a bit more complicated than what it seems as you may need to make sure that the one you decide to keep has all your necessary mapped components. You can drag child objects from one node to another in your mapping to build your final object before you delete.
05-19-2017 07:01 AM
As for why your test runs are sometimes passing and sometimes failing, without knowing what exactly is in your test scripts or cases, it's hard to say. My guess is that, because the same object is in your mapping twice, this may be "confusing" the object identification features of TestComplete as it tries to determine which one to reference when looking at the objects on screen. Again, the solution is to consolidate your mapping into one page object with all the requisite child objects and delete the extraneous object.
05-19-2017 07:46 AM
Thanks for the suggestions,
It is possible that the product has changed during development to cause the page not to be recognised and a new one to be created in the namemapping.
I'll have a look at the delete option, once I've evaluated the objects I need to retain.
05-19-2017 07:49 AM
No problem, man.
Something else to watch for when you start consolidating the mapping. Make sure that your references in all your test cases are updated to point to whatever nodes you are looking for. Again, this could take a little bit of elbow grease to find all references but I think you'll end up with a better test project in the end.
06-09-2017 01:10 AM
Thanks for this. I, copied mapped objects, and then deleted one of the root mapped nodes. Tests are running more reliably now.