feat(core): Add new matchers and improve negation messaging
This commit is contained in:
10
changelog.md
10
changelog.md
@ -1,5 +1,15 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-04-28 - 2.1.0 - feat(core)
|
||||
Add new matchers and improve negation messaging
|
||||
|
||||
- Added expect.any() and expect.anything() matchers for enhanced object pattern matching
|
||||
- Introduced new number matchers: toBeNaN(), toBeFinite(), and toBeWithinRange()
|
||||
- Implemented alias toBeEmpty() for both string and array matchers
|
||||
- Enhanced function matchers with toThrowErrorMatching() and toThrowErrorWithMessage()
|
||||
- Improved negation messaging to provide clearer failure messages (e.g. 'Expected 5 not to be greater than 3')
|
||||
- Enhanced object assertions with a toHaveOwnProperty() shorthand that outputs unified diff-style messages
|
||||
|
||||
## 2025-04-28 - 2.0.1 - fix(assertion-matchers)
|
||||
Refactor matcher implementations to consistently use customAssertion for improved consistency and clarity.
|
||||
|
||||
|
Reference in New Issue
Block a user