I think that Kiran answered the question well, but I just wanted to add a comment or two. You may know this, but it's important to know that navigate, write, and read stages never implicitly wait for an element to load before trying to work with the element. So, as Kiran pointed out, you'd want to use an intelligent wait stage to wait for the entire page to load or wait for a specific element to load or something like that.
If this is a web app, I would suggest using an intelligent wait stage at the beginning of each of your actions that waits for the entire page to finish loading. This only works with an HTML element. The drop-down in the Wait stage line would be either Check Exists, Document Loaded, or Parent Document Loaded. Any of these three are fine to use, but they serve different purposes:
- Check Exists: Waits for an element to be found up to the max timeout
- Document Loaded: Waits for the page to load but does not care about whether any particular element is found and will wait for the full page to load up to the max timeout
- Parent Document Loaded: Waits for the page to load and ALSO waits for the particular element to be found and will wait up to the max timeout. I usually use Parent Document Loaded because it effectively performs the job of both Check Exists and Document Loaded at the same time.
Just wanted to give my thoughts in case it helps!
------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company
