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

Fail to mock class that directly extends java.lang.Object #38

Closed

GoogleCodeExporter opened this issue Nov 18, 2015 · 1 comment

Labels

auto-migrated Milestone-Release1.0 Priority-Critical Type-Defect

GoogleCodeExporter commented Nov 18, 2015

The new constructor suppression algorithm doesn't work for classes that
directly extend from java.lang.Object since Object doesn't contain a ctor
with with argument IndicateReloadClass. We must change the implementation
in the MainMockTransformers' edit(ConstructorCall c) method to check if the
super class is of type Object before defering the call.

Original issue reported on code.google.com by johan.ha...@gmail.com on 24 Oct 2008 at 1:05

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Milestone-Release1.0 auto-migrated Type-Defect Priority-Critical labels

GoogleCodeExporter closed this as completed

Author

GoogleCodeExporter commented Nov 18, 2015

Fixed a serious bug that caused classes extending to java.lang.Object to be 
non-mockable.

Original comment by johan.ha...@gmail.com on 26 Oct 2008 at 9:31

Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment