Skip to content
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.

Sign up for GitHub

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

Jump to bottom

when a mock object is leaked, we should print which test it is from #45

Closed
GoogleCodeExporter opened this issue Jul 13, 2015 · 1 comment
Closed

when a mock object is leaked, we should print which test it is from #45

GoogleCodeExporter opened this issue Jul 13, 2015 · 1 comment
Labels
auto-migrated OpSys-All Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Currently, when we detect a leaked mock object, we print the source file
location where it was first set expectations on.  Sometimes the user do
that in a subroutine shared by several tests, and it's unclear which test
leaked the mock.

We should also print which test method the leaked mock object is from.

Original issue reported on code.google.com by zhanyong...@gmail.com on 4 May 2009 at 5:56
@GoogleCodeExporter
Copy link
Author

Original comment by zhanyong...@gmail.com on 7 May 2009 at 6:09

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated OpSys-All Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter