[Bug]: toThrow does not fail test on mismatch of Error#cause
#15316
Comments
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
|
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
|
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
|
Folks, there's a PR and everything, and it even protects against circular references. Let's land it! |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version
30.0.0-alpha.6
Steps to reproduce
Expected behavior
The test should fail, owing to the mismatch of
Error#cause.Actual behavior
The test passes.
Additional context
This is a re-file of #15111 which was auto-closed for inactivity. Updated to note that this is still a problem in Jest v30.
This appears to be because Jest only does cause-matching when the
causeproperty is an instance ofError.https://github.com/jestjs/jest/blob/main/packages/expect/src/toThrowMatchers.ts#L481-L483
This is inappropriate, since the value of
causeis allowed to be any type.Environment
System: OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish) CPU: (64) x64 AMD EPYC 7502P 32-Core Processor Binaries: Node: 20.16.0 - ~/n/bin/node Yarn: 1.22.22 - ~/.local/share/pnpm/yarn npm: 10.8.1 - ~/n/bin/npm pnpm: 9.9.0 - ~/.local/share/pnpm/pnpm npmPackages: jest: ^30.0.0-alpha.6 => 30.0.0-alpha.6The text was updated successfully, but these errors were encountered: