e2e2275d41
Removed obsolete and unused utility fns
2022-06-11 11:17:16 -07:00
bd368aceee
Replaced var with const and let in expectation related code
2022-06-01 09:22:03 -07:00
7a685b16f6
Removed duplicate message from errors (incl. matcher failures) on V8
2021-11-16 12:52:07 -08:00
8b3a6561b1
Merge branch 'main' into 3.99
2021-04-02 11:35:30 -07:00
60bbe68148
Support source maps
2020-11-05 11:40:04 +01:00
90d6f9d73c
Added deprecation messages to interfaces that will be removed in 4.0
...
* `jasmine.pp`
* `jasmine.matchersUtil`
* Matchers that expect to receive custom equality testers
* Passing custom equality testers to `matchersUtil.contains`
* Passing custom equality testers to `matchersUtil.equals`
2020-02-12 15:24:42 -08:00
b4cbe9850f
add prettier and eslint
2019-05-21 18:23:48 -07:00
d803bd12a6
When catching a global error in Node.js, print the type of error
2018-12-11 08:32:45 +11:00
d4f9b41eda
Print error message when available
...
With the current set up, error message is only printed out when error name is available.
There are situations where the ErrorEvent object does not have a `name` property, but the message is still relevant.
For more details see #1594
2018-09-11 23:25:28 +08:00
05015a8b3e
Correctly format stack traces for errors with multiline messages
...
- Fixes #1526
2018-03-10 12:03:08 -08:00
1923461b09
Ignore more browser fields when formatting Errors
...
- description from IE
- column from Safari
2018-02-27 09:52:19 -08:00
63cc7cafc8
Use Jasmine's arrayContains, instead of includes for better support
2018-02-26 17:57:37 -08:00
1149d4edde
Use j$.pp instead of JSON.stringify() for pretty printing
2018-02-27 10:22:06 +11:00
9ee85c35d2
Remove duplicate ignored property
2018-02-27 10:21:50 +11:00
763a83c833
Display error properties for failed specs
2018-02-23 14:43:47 +11:00
5906a2c05c
Filter Jasmine frames from stack traces
...
[Finishes #2644992 ]
2017-11-13 15:49:01 -08:00
31d71ac22f
add single quote check to jshint and fix src files for that
...
[fixes #522 ]
2014-02-24 16:28:16 -08:00
06a553503d
Better failure message when something is thrown that's not an error
...
Change from 'undefined : undefined' to '<thing that was thrown> thrown'
Pointed out by @charleshansen
2014-01-09 22:10:40 -08:00
aca43bd3a3
Squashed commit of work to make Jasmine a collection of isolated modules. Note now that in our test suite, "jasmine" now always refers to the build jasmine loaded from jasmine.js and "j$" always refers to the code in the src directories.
...
Also, dev_boot.js is now a copy of boot.js and has additional changes to load jasmine the second time, into the j$ reference.
2013-05-28 14:09:20 -07:00
cf7bb0269b
Added grunt to project.
...
Move from embedded "fork" of jsHint to using grunt's jsHint module.
Cleaned ALL jsHint errors.
Added jasmine.util.isUndefined as alternative to extra careful protection against undefined clobbering
2013-03-01 14:28:18 -08:00
d6da13a8dd
Attempt at normalizing error stacks across browsers.
...
Failed expectations now have a `stack` property, remove `trace.stack`
2013-02-27 16:37:31 -08:00
a9eaa66da5
removing the exception formatter from the util namespace
2012-12-09 09:29:05 -08:00
Steve Gravrock