I have added a new timeout parameter to eReferralsApiclient and when this one is configured to soft login, receive 5 seconds as the timeout.
I have refactored SoftloginUseCase to verify against last valid credentials when a timeout is thrown from eReferralsApiclient.
I have added a new test to verify this new logic
:boom: How can it be tested?
1 - Change build variant to ereferralsStaging and execute all unit and instrumentation tests.
2 - Change build variant to ereferralsDebug and remove the app in the device
3 - execute app and verify manually the next use cases:
Change current remoteTimeoutSoftLogin from 5000 milliseconds to lower (getSoftLoginUseCase method in AuthenticationFactoryStrategy).
Use Case 1: start the app realize full login and provoke one action to soft login to appear, for example, close the app and start again. The soft login should work verifying against local.
:floppy_disk: Requires DB migration?
[x] Nope, we can just merge this branch.
[ ] Yes, but we need to apply it before merging this branch.
[ ] Yes, it's already applied.
:art: UI changes?
[x] Nope, the UI remains as beautiful as it was before!
:pushpin: References
:tophat: What is the goal?
:gear: branches
app: Origin: maintenance-change_soft_login_timeout Target: v1.4_connect bugshaker-android: Origin: downgrade_gradle_version EyeSeeTea-sdk: Origin: Development
:memo: How is it being implemented?
:boom: How can it be tested?
1 - Change build variant to ereferralsStaging and execute all unit and instrumentation tests. 2 - Change build variant to ereferralsDebug and remove the app in the device 3 - execute app and verify manually the next use cases:
Change current remoteTimeoutSoftLogin from 5000 milliseconds to lower (getSoftLoginUseCase method in AuthenticationFactoryStrategy).
Use Case 1: start the app realize full login and provoke one action to soft login to appear, for example, close the app and start again. The soft login should work verifying against local.
:floppy_disk: Requires DB migration?
:art: UI changes?