| || |
How to handle frequent hierarchy changes of objs
I'm automating a flex application with QTP 9.5/Flex Addin 3.0. We are currently facing a challenge wherein hierarchy of objects are changing with successive builds. We are updating the object repository with and making necessary hierarchy specific changes in script to run the script successfully. Is there any way to handle frequent hierarchy changes in better way?
Also, one more thing is observed that even appearance of a application is not changed but QTP displays different hierarchy structure for same flex object after relearning. Any pointer whether this it is due to changes in code of flex application OR it can be due to QTP way of learning Flex application ?