Description
Strict mocks in GIDSignInTest 'carry forward' in subsequent tests using mocked objects, like OIDAuthState. If test receiving error is ran before GIDSignInTest, then the test succeeds.
To Reproduce
Steps to reproduce the behavior:
In GIDSignInTest.m, change OCMClassMock to OCMStrictClassMock for OIDAuthState and GTMAuthSession.
Run all tests under GSI Suite.
Expected behavior
Tests in GIDVerifyAccountDetailTest should not error due to OCClassMockObject(OIDAuthState): since no mocking is done in this file.
Additional context
Issue was found in GIDVerifyAccountDetailTest whenever creating a test instance of OIDAuthState (PR). This issue was temporarily fixed to unblock tests by changing the strict mocks to be less restrictive.
Description Strict mocks in
GIDSignInTest
'carry forward' in subsequent tests using mocked objects, likeOIDAuthState
. If test receiving error is ran beforeGIDSignInTest
, then the test succeeds.To Reproduce Steps to reproduce the behavior:
GIDSignInTest.m
, changeOCMClassMock
toOCMStrictClassMock
forOIDAuthState
andGTMAuthSession
.Expected behavior Tests in
GIDVerifyAccountDetailTest
should not error due toOCClassMockObject(OIDAuthState):
since no mocking is done in this file.Error message test failure link
OCClassMockObject(OIDAuthState): unexpected method invoked: initWithAuthorizationResponse:<OIDAuthorizationResponse:
Additional context Issue was found in
GIDVerifyAccountDetailTest
whenever creating a test instance ofOIDAuthState
(PR). This issue was temporarily fixed to unblock tests by changing the strict mocks to be less restrictive.