test for using local active contact if failed to fetch

[tomholub]

This will be a test case to write for @fcvakintos to write after this PR is merged:

1. open compose screen, search robot@flowcrypt.com, wait for it to load. Verify renders as valid.
2. Search for expired@flowcrypt.com and wait for that to load. Verify renders as expired.
3. search for revoked@flowcrypt.com and wait to load. Verify renders as revoked.
4. Remove all recipients.
5. go offline
6. load robot@flowcrypt.com and verify it shows valid while offline (as if you were online)
7. load expired@flowcrypt.com and verify it shows an error while offline (could not load while offline)
8. load revoked@flowcrypt.com and verify it shows an error while offline (could not load while offline)

Originally posted by @tomholub in #1419 (comment)

[tomholub]

This can be written once #1419 merges

[fcvakintos]

@tomholub we cant turn on offline mode in our test, it is not working on IOS
https://appium.io/docs/en/writing-running-appium/other/network-connection/

[tomholub]

In that case, change:

• robot@flowcrypt.com to valid@domain.test
• expired@flowcrypt.com to expired@domain.test
• revoked@flowcrypt.com to revoked@domain.test

And instead of relying on live data, this will be a test that used Attester API mock. After you successfully pull the first 3 public keys, you will update attester mock to start sending error 400 or similar on each request, and retry the three.

The behavior should be same as if the app was offline.

If available mock data for Attester API don't include expired and revoked samples, you can get them from the iOS app by searching the original three emails and then going to Settings -> Contacts -> eg revoked@flowcrypt.com and extract it from there.

[fcvakintos]

@tomholub what Attester API request should i use?

[tomholub]

It's the app that does the API requests. You just drive the UI and app makes requests to the mock.

[fcvakintos]

@tomholub can you provide steps for covering? Im not sure to understand you

[tomholub]

1. set up Attester mock to return a valid public key at valid@domain.test, expired one at expired@domain.test and revoked at revoked@domain.test
2. open compose screen, search valid@domain.test, wait for it to load. Verify renders as valid.
3. Search for expired@domain.test and wait for that to load. Verify renders as expired.
4. search for revoked@domain.test and wait to load. Verify renders as revoked.
5. Remove all recipients.
6. update attester mock to start returning an error
7. load active@domain.test and verify it shows valid
8. load expired@domain.test and verify it shows an error (could not load due to error)
9. load revoked@domain.test and verify it shows an error (could not load due to error)

[fcvakintos]

@tomholub could you provide revoked public key ?

[fcvakintos]

and how can i do this 'update attester mock to start returning an error'?

[tomholub]

Update attester mock code, similar to fes mock code. You'll want to copy and update method throwErrorIfConfigSaysSo. Then update attester config to include returnError?: { code: number, message: string }, similar to fes config.

Then use that newly added config.

[fcvakintos]

@tomholub do you have revoked pubkey?

[tomholub]

see

If available mock data for Attester API don't include expired and revoked samples, you can get them from the iOS app by searching the original three emails and then going to Settings -> Contacts -> eg revoked@flowcrypt.com and extract it from there.