Forum Discussion
In my test, i only open one page, and the url keeps changing so i have given Page(*).
No specific reason to use DOM. Only because the objects on the page takes a bit longer to load, in spinning view for few seconds until all the grids are visible and then it takes a bit longer to go through each grid on the page, hence was exploring options to grab from DOM
You still won't be able to interact with the object until it's fully loaded, even if you go via DOM. The problem is not with TC, it's simply the nature of things.
As for your dynamic URL... you can use wildcards in the URl. Say there's an ID that keeps changing. You could use Page('http://myapp.me.com/app/*') This is preferable to a fully dynamic page.
- tristaanogre6 years agoEsteemed Contributor
Visible is based upon a number of factors to determine if the object is visible. It's not 100% reliable. It's not exactly the best way of determining if you're on the correct page. URL is best for that... and again, any dynamically change factors of the URL can be wildcarded. No need to go with DOM
- tristaanogre6 years agoEsteemed Contributor
If you're using NameMapping, a page object can be mapped using other properties on the page... like page title.
- Mathit6 years agoContributor
thank you,
I was also thinking of DOM for another reason. to verify if Im on the right page before starting to read or enter data in the page. If I use isvisible property of an object, or isexist property of a frame in the page, a lot of times it shows incorrect result. As in, isvisible is true even if it is not visible and same is the case with isexist.
Do you have any suggestion so i dont have to give an explicit wait statement like delay 15000 etc.
- Mathit6 years agoContributor
What if my url is the same when moving from one page to other, what is the best way to validate the page before starting to enter values or retrieve values from the page
- Mathit6 years agoContributor
I have a continue button which appears like this in different browsers. In this case DOM is an option?
CHROME: <input type="button" value="Continue" class="btn btn-success right" ng-click="vm.logic.validateTab(applicantDetails)">
Ie : <input class="btn btn-success right" type="button" value="Continue" ng-click="vm.logic.validateTab(applicantDetails)">
Edge: <input value="Continue" class="btn btn-success right" ng-click="vm.logic.validateTab(applicantDetails)" type="button">
Related Content
- 9 months agoLuukdb
- 9 years agoilovechiku
Recent Discussions
- 21 hours agoGane195