• complete: Within the page wait time, page is required to fully load.
• interactive: Within the page wait time, page is required to load to the point where its DOM elements are accessible.

Suppose that in test case TC 01 you only want to wait until a page finishes loading interactively, so that you can access the DOM elements quickly, including username and password controls. By contrast, in test case TC 02, in order to verify CSS files applied to the given page, your test must wait until a page finishes loading fully.

        
        	setting	value	
setting	page wait state	interactive	
&nbsp			
	window	control	value
enter	home page	username	alex
enter	home page	password	ta
        
    

        
        	setting	value
setting	page wait state	complete
&nbsp		
	expected	
check CSS rules	commonltr.css	
        
    

• The page wait state built-in setting affects the readyState property of a document, the loading state of the document (Learn more).
• Possible values:
  • complete: The document and all sub-resources have finished loading fully.
  • interactive: The document has finished loading and the document has been parsed but sub-resources, such as, images, stylesheets, and frames are still loading. A user, or automation, now can interact with the object, even though it is not fully loaded.
• If your automated test only accesses DOM elements, it is suggested that you set the value to interactive to avoid the case where the page unexpectedly does not finish loading fully within the specified page wait time, despite being available for interaction. By so doing, you can avoid unnecessary automation errors.