ui tests from browser extension - compose

[tomholub]

from #1274

todo tests - minor:

• compose - reply - pass phrase dialog - dialog ok
• compose - reply - pass phrase dialog - dialog cancel
• compose - pass phrase dialog - dialog cancel
• compose - non-primary pass phrase dialog - dialog cancel

purpose of tests unsure:

• compose - standalone- hide/show btns after signing
• compose - check for sender [ci.tests.gmail@flowcrypt.test] from a password-protected email
• compose - check for sender [flowcrypt.compatibility@gmail.com] from a password-protected email
• compose - check for sender [flowcryptcompatibility@gmail.com]
• compose - enter recipient which is not in the contact list
• compose - revoked OpenPGP key (is this for own key revoked? Or recipient? For that we already had compose - revoked recipients trigger revoked warning)
• compose - key-mismatch - standalone - key mismatch loading

tests done:

• compose - revoked recipients trigger revoked warning
• compose - good recipients trigger no warning
• don't auto-refresh expired key if disallowed search on attester
• compose - can choose found contact

todo tests after Gmail mock is available:

• compose - reply - can load quote from plain/html email
• compose - quote - can load quote from encrypted/text email
• compose - quote - can load quote from plain/text email
• compose - reply - signed message with attachment - can be downloaded after send
• compose - reply - can load quote from encrypted/html email
• compose - reply - subject starts with Re:
• compose - recipients are properly ordered
• compose - sending and rendering message with U+10000 code points
• compose - sending a message encrypted with all keys of a recipient

todo functionality first:

• compose - reply all - from === acctEmail (functionality sendAs sendAs support of alias emails #1298 )
• compose - reply all - from !== acctEmail (functionality sendAs sendAs support of alias emails #1298 )
• compose - reply - from === acctEmail (functionality sendAs sendAs support of alias emails #1298)
• compose - reply - from !== acctEmail (functionality sendAs sendAs support of alias emails #1298)
• compose - reply - CC&BCC test forward (functionality adding cc and bcc recipients #954 )
• compose - reply - CC&BCC test reply (functionality adding cc and bcc recipients #954)
• compose - CC&BCC new message (functionality adding cc and bcc recipients #954)
• compose - reply all - TO/CC/BCC when replying all (needs adding cc and bcc recipients #954)
• compose - loading drafts - new message, rendering cc/bcc and check if cc/bcc btns are hidden (needs adding cc and bcc recipients #954)
• compose - sending and rendering encrypted message with image (requires rich text)
• compose - sent message should't have version and comment based on OrgRules
• compose - recipient pasted including name
• compose - nopgp (needs send password-protected messages through web portal #955)
• compose - with attachments + nopgp (needs send password-protected messages through web portal #955 )
• compose - saving and rendering a draft with image (needs rich text and also drafts)
• compose - trying to send PWD encrypted message with pass phrase - should show err (needs send password-protected messages through web portal #955)
• compose - new message, open footer
• compose - new message, Footer Mock Test
• compose - loading drafts - reply (needs more crashes from 0.3.2 - when encrypting drafts #970 )
• cannot import expired key in secure compose (needs ability to import pubkeys in compose when missing, not implemented)
• compose - from alias (needs sendAs support of alias emails #1298)
• compose - settings - manually copied pubkey (no ability to import pubkeys yet)
• compose - sending and rendering plain message with image (needs rich text)

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[github-actions]

There were 2 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.