Significantly clean up the way the scenario DSL works and implement many more DSL statements.

- "this" always means the current chain scope inside a DSL

- addFutureAction callbacks now take ($window, $document, done)

- $document has a special method elements() that uses the currently selected nodes in the document as defined by using() statements.

- $document.elements() allows placeholder insertion into selectors to make them more readable.
  ex. $document.elements('input[name="$1"]', myVar) will substitute the value of myVar for $1 in the selector. Subsequent arguments are $2 and so on.

- $document.elements() results have a special method trigger(event) which should be used to events. This method implements some hacks to make sure browser UI controls update and the correct angular events fire.

- futures now allow custom formatting. By default any chain that results in a future can use toJson() or fromJson() to convert the future value to and from json. A custom parser can be provided with parsedWith(fn) where fn is a callback(value) that must return the parsed result.

Note: The entire widgets.html UI is now able to be controlled and asserted through DSL statements!!! Victory! :)

1 files changed, 1 insertions, 1 deletions

diff --git a/src/scenario/Application.js b/src/scenario/Application.js
index 24ae99e9..4ee0dd03 100644
--- a/src/scenario/Application.js
+++ b/src/scenario/Application.js
@@ -47,5 +47,5 @@ angular.scenario.Application.prototype.navigateTo = function(url, onloadFn) {
  */
 angular.scenario.Application.prototype.executeAction = function(action) {
   var $window = this.getWindow();
-  return action.call($window, _jQuery($window.document), $window);
+  return action.call(this, $window, _jQuery($window.document));
 };