Skip to content

Latest commit

 

History

History
134 lines (85 loc) · 5.42 KB

CHANGELOG.md

File metadata and controls

134 lines (85 loc) · 5.42 KB
Raw

Changelog for jasminewd2

0.1.1

  • (cf1cd34) chore(isPromise): revert expose deferred object's promise (#78)

0.1.0

Release for the selenium-webdriver 3.0.1 upgrade.

0.1.0-beta.1

  • (5fe36a6) deps(selenium-webdriver): upgrade to 3.0.0 (#63)

    fix test "should wait till the expect to run the flow"

    • isPending exists but it is no longer part of ManagedPromise

    • isPending also is no longer exported in lib/promise.js

    • wrote an isPending similar to selenium-webdriver in common.js require a minimum node version

    • selenium-webdriver 3.0.0 requires node >= 6.9.0

    • update travis test to use node 6

0.1.0-beta.0

This beta release is for the selenium-webdriver 3.0.0-beta-3 upgrade.

Dependencies

  • (70c9f62) upgrade(isPromise): expose the deferred object's promise (#58)

    • isPromise checks to see if the input parameter has a then method
    • Deferred class has a promise property and no longer has a then method

  • (8870365) deps(selenium-webdriver): upgrade to 3.0.0-beta-3 (#57)

0.0.10

  • (ff2e624) fix(webdriver): Pass in the control flow.

    BREAKING CHANGE: The control flow now needs to be passed in when using jasminewd. This fixes an issue where having multiple versions of selenium-webdriver in a package's dependency tree would result in jasminewd and protractor using different control flows. You now have to initialize jasminewd before you can use it, like so: require('jasminewd2').init(webdriver.promise.controlFlow());

    See angular/protractor#3505

  • (db26b1a) fix(stacktrace): do not crash if beforeEach block is rejected without any stated reason (#45)

0.0.9

0.0.8

  • (5abc745) chore(jasmine): update MatchFactory to allow message as function

  • (750898c) fix(expectation): expectations without promises no longer add to task queue

    Instead, expectations without promises in either expected or actual are unchanged from the original Jasmine implementation.

    See angular/protractor#2894

0.0.7

  • (55fd11e) fix(index): forward it's return value

  • (f4c30a0) fix: allow empty it functions

0.0.6

  • (4776c16) chore(selenium-webdriver): update selenium webdriver to 2.47.0

    Update selenium-webdriver to 2.47.0 from 2.45.1. This update introduces a convoluted situation where some tests in Proractor's suite would hang - see angular/protractor#2245

    This change includes a fix for those issues which removes the explicit flow.execute wrapper around expect calls. This appears not to introduce any issues to existing tests.

0.0.5

  • (037c7de) chore(dependencies): update Jasmine to 2.3.1

0.0.4

  • (8f8b8b3) tests(context): test that the this variable points to the right thing

    Note: this means that using this.addMatchers no longer works inside before blocks or specs. It should have been changed to jamsine.addMatchers since the upgrade to Jasmine 2. It was still working by accident up until the previous commit.

  • (c0f13d2) refactor(asyncTestFn): refactor async test wrapping to show more info

    Test wrapping for Jasmine 2 now more closely follows the test wrapping for Mocha at https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/testing/index.js

    This also adds more information to the task names in the control flow, for easier debugging.

0.0.3

  • (161e1fa) fix(errors): update webdriverjs, fix asynchronous error output

    Add some console logging, remove useless info about the last running task in the control flow, and fix error where problems reported from done.fail were getting pushed into the following spec.

    Closes #18

  • (fdb03a3) docs(readme): add note about jasmine 1 vs jasmine 2

  • (acaec8b) feat(index): add jasmine2.0 support