-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spyOn property with accessType does not work for instances of a Class #5746
Comments
@phra ideas? |
If you guys don't mind, can I take a stab at this tonight? I'll be using my personal account @thomasjinlo |
nc-lot
changed the title
spyOn property with accessType not working as expected
spyOn property with accessType does not work for instances of a Class
Mar 7, 2018
thomasjinlo
added a commit
to thomasjinlo/jest
that referenced
this issue
Mar 8, 2018
thomasjinlo
added a commit
to thomasjinlo/jest
that referenced
this issue
Mar 8, 2018
thomasjinlo
added a commit
to thomasjinlo/jest
that referenced
this issue
Mar 8, 2018
thomasjinlo
added a commit
to thomasjinlo/jest
that referenced
this issue
Mar 9, 2018
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do you want to request a feature or report a bug?
Feature for
spyOn
to work with objects that have getters/setters on the prototype chain.What is the current behavior?
Does not support spying on getters/setters on the object's prototype chain.
If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can
yarn install
andyarn test
.I have recreated this issue in this repl.
https://repl.it/@functionator/spyOn-getter
What is the expected behavior?
Should be able mock getters/setters on the object's prototype chain.
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
The text was updated successfully, but these errors were encountered: