Forum Discussion
No.. not solved yet.
still looking for an answer.
Hi,
> Set q_textbox = page.NativeWebObject.Find("idStr","updatedQty_0")
Knowing nothing about your tested application, this is what I would try:
-- Set a breakpoint on the line next to the .Find() call, Evaluate found q_textbox object and note the value of its q_textbox.FullName property;
-- Set another breakpoint on the line where you expect to see value of .Text to be equal to 4 and continue execution;
-- When execution stops at the second breakpoint:
-- Highlight UI element that you expect to correspond to the q_textbox object using Object Spy and check: a) if the value of the .Text property equals to 4; and b) if the value of the .FullName property equals to the previously noted one.
If values for FullName do not match, this obviously means that you work with different objects and must search for this another object before using it in test code.
If values for FullName do match, this may mean that the object was recreated somewhere between two breakpoints. Again, in this case you need to search for the same (but recreated) object before validating its value.
Generally speaking, the following workflow should be used when working with dynamic web pages: if the value of some UI object's property in test code does not correspond to your expectation but Object Spy displays correct value for the highlighted UI element, this usually means that the given UI element was recreated and must be searched for anew.
Related Content
- 4 years agoEtrahkad
- 8 years agogdave
- 5 years agodbattaglia