EKM integration new tests - followup

[tomholub]

continuing from #469 (comment)

Once the stuff on above link works, in another PR, we could continue to do the following:

7. restart app and you should see inbox.
8. Open the message again and you should see a pass phrase prompt
9. Try entering wrong pass phrase, and a meaningful error should be shown, and you should be able to try again
10. enter the correct pass phrase and the message should render with the content
11. go back to inbox
12. go back to the message, this time you should be able to read it without pass phrase prompt

Then in yet another PR:

13. go to Settings and you should NOT be seeing Backups section
14. go to Settings -> Keys and you should NOT be seeing an 'add' button
15. in Settings->Keys there should be one key loaded with the right information (fingerprint, date created)
16. when you click on the key, you should NOT be able to export the private key. But you should be still allowed to export or see the public key

After that, I'll file another issues for:

• testing that Attester search is disabled on some domains #736
• testing that WKD is used for looking up public keys #737

[fcvakintos]

@tomholub
About this case:

• restart app and you should see inbox.
• Open the message again and you should see a pass phrase prompt
• Try entering wrong pass phrase, and a meaningful error should be shown, and you should be able to try again
• enter the correct pass phrase and the message should render with the content
• go back to inbox
• go back to the message, this time you should be able to read it without pass phrase prompt

I think it is not actual after fixes for this issue #520

[fcvakintos]

@tomholub about "go to Settings -> Keys and you should NOT be seeing an 'add' button" -> "Add(+)" button is displayed. is it bug or no?

[tomholub]

That's a bug.

[tomholub]

@tomholub About this case:

* restart app and you should see inbox.

* Open the message again and you should see a pass phrase prompt

* Try entering wrong pass phrase, and a meaningful error should be shown, and you should be able to try again

* enter the correct pass phrase and the message should render with the content

* go back to inbox

* go back to the message, this time you should be able to read it without pass phrase prompt

I think it is not actual after fixes for this issue #520

It's still current. #520 only tests that it doesn't ask for pass phrase when opening plain message, but the above is about opening encrypted messages. We want to test that:

• you will see a pass phrase prompt when opening an encrypted message with "pass phrase in memory" setting and before the pass phrase was entered
• pass phrase prompt should show a meaningful error and a retry when I enter wrong pass phrase
• encrypted message should be correctly decrypted after entering the pass phrase
• pass phrase will be remembered if I go back and open the message again

Maybe some of this is already covered by other tests, in which case you can highlight which tests those are. But it's not #520 which is about plain messages.

[fcvakintos]

@tomholub ok, will check

[fcvakintos]

@tomholub can you review?
#730