fix(jasminewd): allow use of custom matchers

Using jasmine.Matchers.prototype to generate the chained methods for
expect() calls is flawed because it does not pick up custom matchers
defined using addMatcher.  Instead, use either the matchersClass for
the current spec or from the environment.

Author: Jeremy Morony

jasminewd/index.js

@@ -90,7 +90,10 @@ function wrapMatcher(matcher, actualPromise) {
  */
 function promiseMatchers(actualPromise) {
   var promises = {};
-  for (matcher in jasmine.Matchers.prototype) {
+  var env = jasmine.getEnv();
+  var matchersClass = env.currentSpec.matchersClass || env.matchersClass;
+
+  for (matcher in matchersClass.prototype) {
     promises[matcher] = wrapMatcher(matcher, actualPromise);
   };
 

jasminewd/spec/adapterSpec.js

@@ -34,6 +34,11 @@ var getFakeDriver = function() {
       return flow.execute(function() {
         return webdriver.promise.fulfilled('b');
       });
+    },
+    getBigNumber: function() {
+      return flow.execute(function() {
+        return webdriver.promise.fulfilled(1111);
+      });
     }
   };
 };
@@ -96,7 +101,13 @@ describe('webdriverJS Jasmine adapter', function() {
   it('should allow scheduling of tasks', function() {
     fakeDriver.sleep(300);
     expect(fakeDriver.getValueB()).toEqual('b');
-  })
+  });
+
+  it('should allow the use of custom matchers', function() {
+    expect(500).toBeLotsMoreThan(3);
+    expect(fakeDriver.getBigNumber()).toBeLotsMoreThan(33);
+  });
+
 
   // Uncomment to see timeout failures.
   // it('should timeout after 200ms', function() {