[WKD mock needed] write UI test for updating keys from WKD

[tomholub]

Works well. I tested the following scenario:

1. loaded demo@flowcrypt.com in compose
2. checked Contacts in app
3. updated EKM to change expiration of the key
4. loaded demo@flowcrypt.com in compose
5. checked contacts - correctly showed new expiration 👍
6. went to EKM to add one more key to demo@flowcrypt.com user
7. went to compose again and added demo@flowcrypt.com
8. went to contacts - now showing two keys for demo@flowcrypt.com 👍

We'll write a UI test for this later. For the UI test to be viable, the WKD has to be mocked.

Originally posted by @tomholub in #710 (comment)

[tomholub]

@fcvakintos this one is harder. You'll need to bring in WKD mock from browser extension (typescript) here:

https://github.com/FlowCrypt/flowcrypt-browser/blob/master/test/source/mock/wkd/wkd-endpoints.ts
https://github.com/FlowCrypt/flowcrypt-browser/blob/master/test/source/mock/all-apis-mock.ts
https://github.com/FlowCrypt/flowcrypt-browser/blob/master/test/source/mock/lib/api.ts
https://github.com/FlowCrypt/flowcrypt-browser/blob/master/test/source/mock/lib/mock-util.ts

Try to keep the structure similar which will make it easier to bring more mocks in. In fact one day we should be able to mock the Google/Gmail API, like we do in browser extension tests.

These mocks start an actual HTTP node server locally.

You'll also have to add 127.0.0.1 recipient.test to hosts file of the ios app.

Also you'll need to make a self-signed https cert, push it to the repo/appium directory, and use that for the mock server (cert + key) and push the certificate as trusted to the iOS emulator OS. So the app can call the mock with https.

Then finally, for the test, type somebody@recipient.test into recipient field, and the mock server will get called to fetch WKD key. For the first prototype, just have the mock always return a 404 but make sure it actually does gets called during the test (eg log something).

In second prototype, the mock should return a public key that the app should recognize. Then I'll help you with the rest of the issue.

[tomholub]

I recommend to do this after all of the other issues as this will take some effort.

[tomholub]

I suppose you'll need the WKD mocks prepared in advance to work on this, so I'm un-assigning.