yesBad/proton-bridge
1
0
Fork 0
forked from Silverfish/proton-bridge
Code Actions Activity

test(GODT-2636): Add step for sending from EML

Browse Source
This commit is contained in:
Gjorgji Slamkov
2023-06-23 06:45:31 +00:00
parent cc1d0e803b
commit 55081fa59b
10 changed files with 189 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
tests/features/imap/message/import.feature
View File

@ -73,7 +73,7 @@ Feature: IMAP import messages
# The message is imported as UTF-8 and the content type is determined at build time.
Scenario: Import message as latin1 without content type
When IMAP client "1" appends "text_plain_unknown_latin1.eml" to "INBOX"
When IMAP client "1" appends "plain/text_plain_unknown_latin1.eml" to "INBOX"
Then it succeeds
And IMAP client "1" eventually sees the following messages in "INBOX":
| from | to | body |
@ -81,7 +81,7 @@ Feature: IMAP import messages
# The message is imported and the body is converted to UTF-8.
Scenario: Import message as latin1 with content type
When IMAP client "1" appends "text_plain_latin1.eml" to "INBOX"
When IMAP client "1" appends "plain/text_plain_latin1.eml" to "INBOX"
Then it succeeds
And IMAP client "1" eventually sees the following messages in "INBOX":
| from | to | body |
@ -89,7 +89,7 @@ Feature: IMAP import messages
# The message is imported anad the body is wrongly converted (body is corrupted).
Scenario: Import message as latin1 with wrong content type
When IMAP client "1" appends "text_plain_wrong_latin1.eml" to "INBOX"
When IMAP client "1" appends "plain/text_plain_wrong_latin1.eml" to "INBOX"
Then it succeeds
And IMAP client "1" eventually sees the following messages in "INBOX":
| from | to |