Bug 439617

Description Bartosz Grabski 2014-07-15 09:21:08 EDT

Editor should provide a way to access the state of itself. It could streamline the UI automation and make tester's life much easier :)

Right now UI automation is highly dependant on timeouts. This can lead to failures when the server backend responds slower than anticipated. Moreover DOM elements could not be fully initialized.

Providing aforementioned interface to access Editor state would lead to more robust and elegant UI automation code.

We could expose the state in several ways. The two i have in mind are:
- creating an orionEditor object in the global window object. The former would hold the state.
- holding the state in a proper requireJS module. Writing UI automation would require accessing the module first.

Java WebDriver sample code that could do the work, 

Boolean isReady = ((JavascriptExecutor) driver).executeJavascript(
	"return window.orionEditor.isReady;"
)

or 

Boolean isReady = ((JavascriptExecutor) driver).executeJavascript(
	"var editorModuleState = require(["editor"], function(editor) { return editor.state });" +
	"return editorModuleState;"
)

and then creating a fluent wait which waits until the Editor is fully loaded is really simple and elegant

Wait<WebDriver> wait = new WebDriverWait(driver, max_timeout);
wait.until(new Function<WebDriver,Boolean> {
	public Boolean	apply(driver) {
		return ...... <- Javascript invocation
	}
}