You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem? 1. Keeping PowerMock.expectNew for super class constructor do not work while testing inheriting class's constructor. I understand that expectnew is not a way to intercept call to Super.
2.MockGateWay constructorCall gets executed which only looks for Suppressions but not for newSubstitutions of MockRepository
3.PowerMock is a dream-tool, so getting the superclass-constructor intercepted is not possible?
Hi
To rephrase the question: how to just expect a super class constructor call to TEST
"Our inheriting class did try to call the super class constructor" while we are also say suppressing the super-class constructor.
Here the Test Motive is only to test there was a effort to call the same.
From bahatan...@gmail.com on March 12, 2013 12:36:16
What steps will reproduce the problem? 1. Keeping PowerMock.expectNew for super class constructor do not work while testing inheriting class's constructor. I understand that expectnew is not a way to intercept call to Super.
2.MockGateWay constructorCall gets executed which only looks for Suppressions but not for newSubstitutions of MockRepository
3.PowerMock is a dream-tool, so getting the superclass-constructor intercepted is not possible?
Using latest powermock version for easymock.
Original issue: http://code.google.com/p/powermock/issues/detail?id=434
The text was updated successfully, but these errors were encountered: