Forum Discussion
TestComplete is not going to automatically change the mapping because it has no way of knowing if that change in the name is a bug or something you expect to happen.
I would think it's something more like
buttonkeep*
What does the mapping look like if you map it right now, for buttonkeep10 or whatever the current value is?
NameMapping.Sys.browser.pageCruisehbApptest.buttonKeep11
//div[14]/div/div/div/div/button[contains(@class, 'fr-keep-word')]
or //div[14]/div/div[2]/div/div/button[2]
or //button[.='Keep?*']
The other ones are very similar except that they will have the //button[.='Keep?*'] as the first item.
The system will change this every time I recreate a new deal it will want a different buttonkeep number..
- Largent8034 years agoContributor
I just re-did the test and again its now up to buttonKeep15. Basically, I can look up the old Namemapping and see the other mapped objects from other times I have run the test and they do include the old mapped steps but since it is showing up as a new test it is wanting to remap to a new buttonKeep with new number. I need it to stop doing this because this is just to save the data into the textbox when the test gets finished it is completely done as with the data in the textnode. So the button is for saving to the textnode and is correct. My checkpoints validate the data as I am working through it.
- Marsha_R4 years ago
Champion Level 3
Delete all but one of the old name mappings and change that one to buttonkeep*
- Largent8034 years agoContributor
The system still comes up wanting to remap the buttonKeep. I have tried adding a buttonKeep?* and a *.*
Basically, it is wanting to remap everytime I rerun the test. Which would be often. I need to make it so that it will allow me to set
it up once and then be able to run the test over and over again.