164a393932
Move spec begin and end handling from Env/SuiteBuilder to TreeRunner
2025-08-23 09:03:57 -07:00
759a867094
Backfill unit tests for spec autoCleanClosures
2025-08-23 09:03:57 -07:00
f94d0ceda9
Validate queueableFns
2025-08-23 09:03:38 -07:00
8d99f27be8
Throw an Error rather than a string when createSpyObj is called incorectly
2025-08-23 08:19:11 -07:00
63774597f0
Extract tree running out into a separate class
2025-08-18 16:50:04 -07:00
a3e1abfa12
Split the resulting execution tree out from TreeProcessor
2025-08-17 11:44:52 -07:00
b89a870a59
Test TreeProcessor's public interface, not internal state
2025-08-17 11:44:37 -07:00
ea3fc88803
Remove mutual recursion between Runner and TreeProcessor
2025-08-17 11:44:36 -07:00
d5884e33c6
Move suite execution and spec queueRunner building from TreeProcesor to Runner
...
This:
* Sets the stage for getting suite and spec execution in one place
* Greatly simplifies the interaction between Runner and TreeProcessor
* Focuses TreeProcessor more on building execution trees
2025-08-17 11:43:00 -07:00
138bf9be4b
Focused integration tests for Runner and TreeProcessor
...
These are mostly adaptations of the execution tests from TreeProcessorSpec.js.
They are meant to support refactoring of the interface and responsibility
division between Runner and TreeProcessor. All these scenarios are probably
covered by nearly-end-to-end integration tests, but those are more difficult
to debug.
2025-08-17 09:23:29 -07:00
98d5284c19
Check for and silence suite reentry warnings in Jasmine's own tests
2025-08-15 06:58:08 -07:00
2299c85751
Deprecate spec/suite orders that interleave suites
2025-08-13 19:02:36 -07:00
8e3ec25f6d
Move invalid order exception throw into TreeProcessor
2025-08-13 18:30:51 -07:00
b009cd2922
Convert TreeProcessor to a class
2025-08-12 18:23:57 -07:00
8eee6ebb91
Runner: naming improvements, use private members
2025-08-11 23:22:07 -07:00
c15a1aaa6d
Rename queueRunnerFactory to runQueue throughout
2025-08-11 23:05:56 -07:00
5b06531cac
Prevent GloablErrors from being monkey patched
...
All current shipped versions of zone.js contain a monkey patch that fails
to pass constructor arguments on to GlobalErrors. That would crash Jasmine
if it was applied early enough to have any effect.
See <https://github.com/angular/angular/issues/63072 >.
2025-08-11 18:08:47 -07:00
42cca93926
Minor jsdoc cleanup
2025-08-09 08:35:49 -07:00
395ef85954
Optionally detect late promise rejections and don't report them as errors
2025-08-09 08:35:08 -07:00
5e88fde655
Backfill some unit tests for Runner's interaction with TreeProcessor
2025-07-29 09:59:45 -07:00
bb777e93e5
Bump version to 5.9.0
2025-07-19 08:27:17 -07:00
9d3fb167a2
Document that the filename property of suite and spec results is deprecated
...
See <https://github.com/jasmine/jasmine/issues/2065 >.
2025-07-19 06:54:54 -07:00
3176eaf1d8
Merge branch 'idConflict' of https://github.com/atscott/jasmine
...
* Avoid generating timers with IDs that conflict with native
* Fixes #2068
* Merges #2069 from @atscott
2025-07-15 16:50:57 -07:00
d31a431d1f
fix(clock): Avoid generating timers with IDs that conflict with native
...
This commit attempts to ensure that the timers created by jasmine mock
clock do not conflict with the native timers. This also retains
pre-existing behavior whereby a native scheduled function cannot be
cleared if it was created prior to the mock clock being installed
(unless the mock clock is uninstalled first).
Prior to this commit, attempting to clear a native timer would result in
clearing a mocked scheduled function instead, in some scenarios where
the IDs conflicted.
fixes #2068
2025-07-14 16:55:05 -07:00
84f78c1435
Split GlobalErrors into portable and platform-specific parts
2025-07-12 13:59:19 -07:00
ff476b1982
Unify error dispatching between browser and node
2025-07-12 13:56:58 -07:00
d53d2ff3eb
Convert GlobalErrors to an ES6 class
2025-07-12 13:56:50 -07:00
adfbd00c75
Refactor mocking in GlobalErrorsSpec
2025-07-12 13:56:48 -07:00
495e5fcd50
Backfill integration tests for unhandled promise rejections
2025-07-11 21:36:30 -07:00
bc2aa7be25
Start breaking up integration/EnvSpec.js
2025-07-11 07:39:39 -07:00
af04599bb5
Relaxed timeout on flaky test
2025-07-09 06:56:08 -07:00
21db6ec0e3
Removed unnecessary errorWithStack helper
2025-06-22 12:49:26 -07:00
2d07b3e6d7
Removed protections against user code redefining undefined
...
Jasmine hasn't even run on platforms that allowed redefining undefined
since 2.x.
2025-06-22 12:23:18 -07:00
6891789ed2
Don't test on Node versions before 18.20.5
...
18.20.5 is the oldest version supported by current selenium-webdriver.
Also, many dev dependencies require at least 18.18.0.
2025-06-14 10:22:03 -07:00
7a3d3c9360
Removed shelljs dev dependency
2025-06-14 09:05:12 -07:00
1b2922e008
Don't hardcode temp dir in buildStandaloneDist
2025-06-14 09:05:12 -07:00
bd8d23f2a7
Removed rimraf dev dependency
2025-06-14 09:05:06 -07:00
de26763868
CI: remove special case for Chrome
2025-06-09 15:05:50 -07:00
f4be08b657
Bump version to 5.8.0
2025-06-06 17:34:09 -07:00
50ef882a1a
Merge branch 'gh1886-spy-args-deep-clone' of https://github.com/evanwalsh/jasmine
...
Merges #2062 from @evanwaslh
Fixes #1886
2025-06-05 06:54:37 -07:00
c1cd5c6291
Use custom object formatters in spy strategy mismatch errors
2025-06-05 05:46:29 -07:00
63ed2b3948
Include function names in pretty printer output
...
This helps make matcher errors and spy strategy mismatch errors easier
to understand in cases where the difference involves expecting one
function but getting a different one.
2025-06-04 18:37:44 -07:00
0183acc682
Fix diff building when only one side has a custom object formatter
...
Fixes #2061
2025-06-04 18:04:40 -07:00
e15819c0dd
Test aginast Node 24
2025-05-27 17:32:39 -07:00
f694194b2b
Allow passing a function to saveArgumentsByValue to customize how arguments are saved
...
For instance, pass `structuredClone` to do a deep clone.
Fixes https://github.com/jasmine/jasmine/issues/1886
2025-05-27 15:43:21 -04:00
94c00886a6
Merge branch 'setimmedate' of https://github.com/atscott/jasmine
...
Merges #2058 from @atscott
2025-05-03 10:00:41 -07:00
f5915d7963
Bump version to 5.7.1
2025-05-01 19:31:30 -07:00
15587f3ce3
Merge branch 'autotickuninstall' of https://github.com/atscott/jasmine
...
Merges #2057 from @atscott
2025-05-01 16:46:30 -07:00
3ecddc2555
fixup! fix(Clock): Ensure that uninstalling the clock also stops auto tick
2025-05-01 10:25:24 -07:00
6a7c0e6368
perf(clock): use setImmediate for autoTick macrotask in Node
...
When called within an I/O cycle, `setImmediate` is generally faster because it
is designed to execute immediately after the current I/O event completes,
whereas `setTimeout(0)` gets placed in the timers queue and might be subject to delays.
> The main advantage to using setImmediate() over setTimeout() is setImmediate()
> will always be executed before any timers if scheduled within an I/O cycle,
> independently of how many timers are present.
* https://nodejs.org/en/learn/asynchronous-work/event-loop-timers-and-nexttick#setimmediate-vs-settimeout
* https://nodejs.org/en/learn/asynchronous-work/event-loop-timers-and-nexttick#poll
* https://nodejs.org/en/learn/asynchronous-work/understanding-setimmediate
2025-04-30 14:10:39 -07:00
Steve Gravrock