-
Notifications
You must be signed in to change notification settings - Fork 3.3k
chore(deps): update dependency chai to v3 #31558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
See the guidelines for reviewing dependency updates for info on how to review dependency update PRs. |
cypress
|
Project |
cypress
|
Branch Review |
renovate/chai-3.x
|
Run status |
|
Run duration | 09m 49s |
Commit |
|
Committer | Jennifer Shehane |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
0
|
|
2
|
|
0
|
|
260
|
View all changes introduced in this branch ↗︎ |
UI Coverage
44.19%
|
|
---|---|
|
72
|
|
57
|
Accessibility
94.9%
|
|
---|---|
|
0 critical
6 serious
0 moderate
1 minor
|
|
123
|
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
This PR contains the following updates:
1.10.0
->3.5.0
Release Notes
chaijs/chai (chai)
v3.5.0
: / 2016-01-28Compare Source
For
assert
fans: you now haveassert.includeDeepMembers()
which matchesexpect().to.include.deep.members()
and.should.include.deep.members()
!This release also includes a variety of small bugfixes and documentation fixes. Most notably, we are now governed by a Code Of Conduct - which gives Chai contributors (including those who files issues, work on code, or documentation, or even just hang out on our Slack & Gitter channels) safety from harassment and discrimination.
Full changes below:
Community Contributions
assert.includeDeepMembers()
. By @qbolecDocumentation fixes
v3.4.1
: / 2015-11-07Compare Source
This is a small documentation bug fix release - it just fixes a couple of issues with the documentation.
Community Contributions
Documentation fixes
.throws()
example. By @Pklongv3.4.0
: / 2015-10-21Compare Source
This release improves some confusing error messages, and adds some new assertions. Key points:
expect(1).oneOf([1,2,3])
- for asserting that a given value is one of a set..include()
(and variants) will now give better error messages for bad object types. Beforeexpect(undefined).to.include(1)
would say "expected undefined to include 1", now says "object tested must be an array, an object, or a string but undefined given".throw()
(and variants) can now better determine the Error types, for exampleexpect(foo).to.throw(node_assert.AssertionError)
now works..closeTo
is now aliased as.approximately
.empty
changes from 3.3.0 have been reverted, as they caused breaking changes to arrays which manually set keys.Community Contributions
Code Features & Fixes
expect(inList).to.be.oneOf
assertion. By @DroogansDocumentation fixes
new Error
type gets detected by thea
/an
matcher. By @jurko-gospodneticv3.3.0
: / 2015-09-08Compare Source
This release adds some new assertions and fixes some quite important, long standing bugs. Here are the cliff notes:
frozen
,sealed
orextensible
assertions to test primitives (e.g.expect(1).to.be.frozen
), you may have noticed that in older browsers (ES5) these fail, and in new ones (ES6) they pass. They have now been fixed to consistently passassert
interface has been given the following new methods, to align better with other interfaces:,assert.isAtMost
,assert.isAtLeast
,assert.isNotTrue
,assert.isNotFalse
.Community Contributions
Code Features & Fixes
assert.isNotTrue
andassert.isNotFalse
.By @cezarykluczynski
frozen
/extensible
/sealed
assertions behave the same in ES6 and ES5 environments.By @astorije
.empty
assertion.By @Daveloper87
assert.isAtMost
andassert.isAtLeast
.By @wraithan
By @kpdecker
Documentation fixes
isBelow
,isAbove
,isTrue
).By @cezarykluczynski
v3.2.0
: / 2015-07-19Compare Source
This release fixes a bug with the previous additions in
3.1.0
.assert.frozen
/expect().to.be.frozen
/.should.be.frozen
all accidentally calledObject.isSealed()
instead. Now they correctly callObject.isFrozen()
.If you're using these features, please upgrade immediately.
It also adds aliases for a lot of
assert
methods:Community Contributions
Code Features & Fixes
By @keithamus
By @couchand
getProperties()
utilityBy @jluchiji
By @jluchiji
By @astorije
By @astorije
v3.1.0
: / 2015-07-16Compare Source
This release adds assertions for extensibility/freezing/sealing on objects:
It also adds assertions for checking if a number is NaN:
Community Contributions
Code Features & Fixes
By @bradcypert
By @matthewlucock
version
property from bower.json.By @kkirsche
v3.0.0
: / 2015-06-04Compare Source
This release contains some small breaking changes. Most people are unlikely to
notice them - but here are the breaking changes:
you're using RequireJS with Chai, you might notice a change (chai used to
be a global, now it won't be - instead you'll have to
require
it)..has.property('foo', undefined)
will now specifically test to make surethat the value
'foo'
is actually undefined - before it simply tested thatthe key existed (but could have a value).
.to.be.a('type')
has changed to support more types, including ES6 typessuch as
'promise'
,'symbol'
,'float32array'
etc, this also means usingES6's
Symbol.toStringTag
affects the behaviour.to.be.a()
. In addition tothis, Errors have the type of
'error'
.assert.ifError()
now follows Node'sassert.ifError()
behaviour - in otherwords, if the first argument is truthy, it'll throw it.
Community Contributions
Code Features & Fixes
assert.ifError()
behaves like Node.js: it throws if the first argument is present.By @cjqed
^1.0.1
By @keithamus (special thanks to @simonzack for his work on assertion-error)
By @Charminbear
.matches()
as alias for.match()
.By @thejameskyle
By @csnover
.property('foo', undefined)
now actually checks to see ifobj.foo === undefined
(before it did not).By @onefifth
By @keithamus
Documentation fixes
.assert()
By @astorije
By @keithamus
.keys()
By @astorije
.length(n)
from the docs - use.lengthOf(n)
instead.By @valscion
.length(n)
examples to.lengthOf(n)
instead.By @keithamus
assert.notInclude
docsBy @BinaryMuse
v2.3.0
Compare Source
==================
make test-firefox
ownPropertyDescriptor
assertion.v2.2.0
Compare Source
==================
.deep
flag..deep
flag..deep.property
v2.1.2
Compare Source
==================
git summary
in READMEv2.1.1
Compare Source
==================
v2.1.0
Compare Source
==================
v2.0.0
Compare Source
==================
.keys(object)
by
cleanup.by
for #333change
to work w/ non-number values + testschange
(#330)change
,increase
,decrease
assertions (#330)change
,increase
,decrease
change
,increase
,decrease
undefined
value pass property assertionConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.