admin/jasmine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2,079 Commits 1 Branch 0 Tags
c395c525dcb4dab6c030dce49557fb3faaa06b8f
Commit Graph

145 Commits

Author SHA1 Message Date
Steve Gravrock
a497d0942a Report async expectations that complete after the runable completes 
It's very easy to forget to `await` or `return` the promise returned
from `expectAsync`. When that happens, the expectation failure will
occur after the spec or suite's result has been reported to reporters,
and the failure will typically not be shown to the user. This change
adds a top-level suite failure in that case, similar to the way we
report unhandled exceptions or promise rejections that occur after the
runable completes. Adding the error at the top level gives us the best
chance of getting in before the set of failures we add it to is sent
to reporters.

See #1752.
 2019-09-27 18:31:01 -07:00
Steve Gravrock
68f25a758d Don't create env instances in beforeEach 2019-09-11 13:31:01 -07:00
Steve Gravrock
2d3ac38df8 toBeRejectedWithError can expect the error to be Error, not just a subtype 2019-09-06 14:17:52 -07:00
Steve Gravrock
5a219da848 Added basic integration tests for all built-in matchers 2019-09-06 14:10:16 -07:00
Dmitriy T
7263a38c3f Adds new configuration option to failSpecWithNoExpectations that will report specs without expectations as failures if enabled 2019-09-05 09:47:38 -07:00
Tony Brix
f77ee32c56 Add custom async matchers 2019-08-30 09:30:14 -07:00
Pivotal
008b80adc5 Merge branch 'enelson/default' of https://github.com/elliot-nelson/jasmine 
* Merges #1716 from @elliot-nelson
 2019-08-29 13:50:27 -07:00
Steve Gravrock
18195a868c Updated async timeout message 
There are now multiple ways to do async functions, and callbacks
are probably the least common in new code, so the message should
be more general rather than referring to callbacks.
 2019-08-03 08:25:57 -07:00
Elliot Nelson
96786c793f Allow users to set a default spy strategy 2019-06-07 23:32:13 -04:00
johnjbarton
a8c2399dd8 feat(result.duration): report test duration in ms 
Wrap spec start/complete in Timer start/elapsed.
configuration.timeSpecDuration = false will disable feature.

 * Add Suite result.duration, elapsed time in ms

 * Remove timeSpecDuration option.

 * Respond to review, use noopTimer
 2019-03-14 09:13:57 -07:00
Felix Rilling
dde93ade18 Fixed typos in comments. 2019-03-10 11:04:33 +01:00
Gregg Van Hove
4991f2a713 Merge branch 'print_global_error_type' of https://github.com/jbunton-atlassian/jasmine into jbunton-atlassian-print_global_error_type 
- Merges #1632 from @jbunton-atlassian
 2019-02-11 09:02:16 -08:00
johnjbarton
c36a005893 Support Error.stack in globalErrors. 
See https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/onerror#window.onerror
 2019-01-03 16:14:23 -08:00
James Bunton
d803bd12a6 When catching a global error in Node.js, print the type of error 2018-12-11 08:32:45 +11:00
Gregg Van Hove
92d0882a32 Introduce a configuration object to Env deprecating old single use functions 
[finishes #159158038]
 2018-09-25 17:08:41 -07:00
Gregg Van Hove
110c092c9e Fix regular expressions for different browsers 2018-06-18 17:55:24 -07:00
Ilya Konstantinov
8c1b80daae Improve Jasmine timeout error message 2018-06-18 17:36:43 -07:00
Steve Gravrock
9472df0db4 Added a basic set of async matchers 
- Fixes #1447
- Fixes #1547
 2018-06-04 21:07:44 -07:00
Gregg Van Hove
8f7327cb4d Properly cascade StopExecutionError's up the tree 
- Fixes #1563
 2018-05-30 17:32:14 -07:00
Gregg Van Hove
7e14a97371 Explicitly pass in timing functions in mock clock integration specs 
- This way we can make sure that clear stack always works no matter
  how long the suite in the spec is

[fixes #153518103]
 2018-04-23 17:25:11 -07:00
Gregg Van Hove
c440d13754 Use the same global for everything in Env 
- No longer use `getGlobal` for clearStack and QueueRunner
 2018-04-13 17:14:48 -07:00
Gregg Van Hove
11f4d894a6 Merge branch 'node-load-errors' 
- See #1519
 2018-02-26 16:44:45 -08:00
sylhare
7fb53dcdfa Fixing missing semi-colons 2018-02-21 09:01:24 -05:00
Steve Gravrock
1ac2a6f608 Allow node to report load time errors 
[Fixes #153466462]
 2018-02-17 15:45:42 -08:00
Tony Brix
6193bc113b throw errors 2018-02-08 15:12:14 -06:00
Tony Brix
c859128537 add tests 2018-02-07 23:58:26 -06:00
Gregg Van Hove
764d58a7f5 Merge branch 'master' into 3.0-features 
- cleaning up 2.99 deprecations
 2018-02-06 09:31:51 -08:00
Gregg Van Hove
24bf3489dc Display deprecation warnings in HTML reporter 
- Also no longer check for stack since IE doesn't do that

[#154746527]
 2018-02-05 12:11:36 -08:00
Gregg Van Hove
5afe1222f4 Add ability to report deprecation warnings from within the suite 
[#154746527]
 2018-02-05 11:19:15 -08:00
Gregg Van Hove
e15f273f06 Replace old "catch exceptions" logic with proper fail fast with error reporting 
- Option is called stopOnSpecFailure

[#85966014]
- See #414
- See jasmine/jasmine-npm#16
 2018-01-30 11:36:56 -08:00
Gregg Van Hove
e908b67b19 Move explicit fail spec out of mock clock context and re-add the afterAll for IEs 2018-01-29 17:05:54 -08:00
Gregg Van Hove
46cc48ccfa Detect an Error passed to done and add an expectation failure 
- See #567
 2018-01-29 16:46:30 -08:00
Gregg Van Hove
50cd6fdd68 Allow reporter callbacks to be asynchronous 
[finishes #154673961]
- Fixes #842

Signed-off-by: Elenore Bastian <ebastian@pivotal.io>
 2018-01-29 11:55:41 -08:00
Gregg Van Hove
6b156ca6d1 Unify status for xdescribe and xit 
- Ensure *All's only execute if at least one child will run
- Specs will report a status of `excluded` instead of disabled

[finishes #153967580]
- #1418

Signed-off-by: Elenore Bastian <ebastian@pivotal.io>
 2018-01-25 16:17:31 -08:00
Elenore Bastian
12a47f05bf Suite level errors all report the same way (on suiteDone) 
- For `beforeAll`, `afterAll`, and declaration errors

[#150118881] #1409

Signed-off-by: Gregg Van Hove <gvanhove@pivotal.io>
 2018-01-23 10:15:28 -08:00
Gregg Van Hove
f20f78f82b Don't clobber previous custom plans with later plans 
[finishes #37288941]
 2018-01-22 12:10:24 -08:00
Steve Gravrock
170a6dce76 Made naming somewhat less confusing 2018-01-10 09:00:09 -08:00
Steve Gravrock
4934e420b2 Allow adding custom spy strategies 
[#37288941]
 2018-01-10 08:59:19 -08:00
Steve Gravrock
ef9f82a17d Merge branch 'master' into 3.0-features 2017-12-18 09:48:17 -08:00
Steve Gravrock
eb93d38294 Allow jasmine-npm to handle its own load errors 
[Fixes #153466462]
 2017-12-08 09:17:10 -08:00
Steve Gravrock
98ead94c51 Fixed spec failure on Chrome 2017-12-01 08:28:55 -08:00
Steve Gravrock
18ed34e9be Fixed failing specs 2017-11-29 09:32:12 -08:00
Steve Gravrock
f4caf27208 Fixed pending() for async/promise-returning specs 
Fixes #1449.
Fixes #1450.
 2017-11-29 08:57:29 -08:00
Steve Gravrock
db615e4186 Determine overall status in core, not reporters 
[#92261606]
[#78679648]
 2017-11-17 14:24:12 -08:00
Steve Gravrock
419470e9df Removed support for IE <10 
[#150527985]
 2017-11-08 08:30:22 -08:00
Steve Gravrock
1526d5e2a8 Treat afterAll errors at any level as failures 
[Finishes #152492514]
 2017-11-07 20:48:23 -08:00
Steve Gravrock
82eeed3c85 Improved reporting of load errors and afterAll errors 
- Pass file and line number to reporters when present
- Show file and line number in the HTML reporter when present
- Visually separate adjacent errors in the HTML reporter

[#24901981]
 2017-11-04 10:28:42 -07:00
Steve Gravrock
ae9b95269c Load error handling doesn't depend on browser features, so test it everywher 
[#24901981]
 2017-11-02 18:17:40 -07:00
Steve Gravrock
26a7bc6acf Report loading errors as loading errors, not afterAll errors 
[#24901981]
 2017-11-01 14:09:29 -07:00
Steve Gravrock
bd250f27c7 Fail if error events (e.g. syntax errors) occur during loading 
[#24901981]
 2017-10-31 21:16:00 -07:00