Permalink
Commits on Sep 20, 2017
Commits on Jul 5, 2017
  1. 7.1.1

    domenic committed Jul 5, 2017
  2. Make ESLint a devDependency instead of a dependency

    domenic committed Jul 4, 2017
    It was put in the wrong category in 16dde11.
Commits on Jul 2, 2017
  1. 7.1.0

    domenic committed Jul 2, 2017
  2. Fix proxies for property assertions (#205)

    meeber authored and domenic committed Jul 2, 2017
    This PR fixes Chai 4's proxy protection for property assertions. Without this fix, proxy protection works for method assertions and chainable method assertions, but not property assertions. The reason it doesn't work for property assertions is because the getters for property assertions incidentally de-proxify the assertion object before returning it. This PR re-proxifies those de-proxified assertion objects from property assertions before returning them.
Commits on Jun 11, 2017
  1. 7.0.0

    domenic committed Jun 11, 2017
  2. Convert tests away from CoffeeScript

    domenic committed Jun 11, 2017
    Also make them stop relying on global setup.
  3. Add a note about using other Chai plugins

    domenic committed Jun 11, 2017
    Closes #145.
  4. Update for Chai v4.0

    meeber authored and domenic committed Dec 17, 2016
    Closes #157. Closes #198.
  5. Various cleanups and updates

    domenic committed Jun 11, 2017
    - Switch ESLint for JSHint
    - Start enforcing the use of newer syntax (as long as it's Node v4 compatible)
    - Add .editorconfig
    - Remove old dependencies no longer needed as of bb51e07
    - Add package-lock.json
    - Use inline Markdown links in the readme
Commits on Sep 27, 2016
  1. 6.0.0

    domenic committed Sep 27, 2016
  2. Update copyright year

    domenic committed Sep 27, 2016
  3. Switch to pure CommonJS

    domenic committed Sep 27, 2016
    Now that we have dependencies, anything else is just fiddly.
  4. Load check-error in the browser too

    lddubeau authored and domenic committed Sep 18, 2016
  5. Bring promise rejection tests in line with Chai.

    lddubeau authored and domenic committed Sep 15, 2016
    chai-as-promised's `.rejectedWith` and `assert.isRejected` now mirror how Chai's `.throws` works. Fixes #47.
  6. Fix the .not.rejectedWith tests

    lddubeau authored and domenic committed Sep 14, 2016
    In Chai `foo.should.not.throw(Constructor, 'string')` would fail only if the error thrown is an instance of `Constructor` **and** if its message includes `'string'`. An instance with a different message would not cause a failure. An instance constructed by something else than `Constructor` would not cause a failure.
    
    .not.rejectedWith's semantics were incompatible with the above.
    
    This commit fixes the test to work according to the correct semantics.
  7. Use check-error to get expected constructor name

    lddubeau authored and domenic committed Sep 9, 2016
    We now use the check-error package to get the constructor name of the error we expect to get with `rejectedWith`. For recent versions of Chai, this makes `rejectedWith` consistent in behavior with Chai's `throw`.
    
    Fixes #64.
  8. Redesign UMD code to allow imports

    lddubeau authored and domenic committed Sep 9, 2016
  9. Allow chaining tests and promises.

    lddubeau authored and domenic committed Sep 9, 2016
    - `.fulfilled`, `.not.rejected` and `.not.rejectedWith` when successful: the promise they return is fulfilled with the same value as the promise they were testing.
    - When `.not.fulfilled`, `.rejected` and `.rejectedWith` are successful: The promise they return is fulfilled with the rejection reason.
    
    In all cases, when they fail, the promise they return is rejected and has for reason the assertion that failed.
    
    The changes above make it so that the `object` flag is automatically set when the promise returned is resolved, and thus also allows chaining.
    
    This fixes #113.
  10. Add a notMessage option

    lddubeau authored and domenic committed Sep 8, 2016
    The problem with issue #47 is that chai-as-promised somtimes treats the final string parameter as a custom error message. We want to test that it does not do this anymore so we check to make sure that such string is not used as a custom error message.
  11. Restructure to avoid so much nesting

    lddubeau authored and domenic committed Sep 8, 2016
  12. Add test cases that reproduce issue #113

    lddubeau authored and domenic committed Sep 8, 2016
  13. Add a case that replicates issue #64

    lddubeau authored and domenic committed Sep 8, 2016
  14. Add test cases to cover issue #47

    lddubeau authored and domenic committed Sep 8, 2016
    The problem is that expect().to.be.rejected/rejectedWith (and its negation) does not mirror how expect().to.throw (and its negation) behave.
    
    Same issue with assert.isRejected in relation to assert.throws.
Commits on Aug 5, 2016
  1. Test stable Node on Travis

    domenic committed Aug 5, 2016
    Closes #164.
Commits on May 24, 2016
  1. Add a link to how to use with Angular

    domenic committed May 24, 2016
    Fixes #150.
Commits on May 11, 2016
Commits on Mar 20, 2016
  1. 5.3.0

    domenic committed Mar 20, 2016
Commits on Mar 15, 2016
  1. Support jQuery >= 3.0.0

    mgol committed Aug 25, 2015
Commits on Dec 20, 2015
  1. Version 5.2.0

    domenic committed Dec 20, 2015
  2. Update dev dependencies

    domenic committed Dec 20, 2015