Add xpcshell tests for message filtering on EWS folders
Categories
(MailNews Core :: Networking: Exchange, task)
Tracking
(Not tracked)
People
(Reporter: benc, Unassigned)
References
(Blocks 1 open bug)
Details
Actually, basic filter tests should work across EWS/IMAP/POP3/whatever, but the existing filter tests are a little IMAP-centric.
(and the EWS filtering operates on incoming messages after they've been added to the folder, unlike IMAP and POP3 which can apply filters before the message is added - way more complicated)
Off the top of my head, here are some things I'd like to test:
Check matching for:
- filter terms which operate solely on fields in
nsIMsgDBHdrobjects (recipients etc)- check with fields which can have multiple values (eg cc list)
- terms which require full message body
- filtering is deferred until after the full message has been downloaded (could be any amount of time before that happens)
- terms which match headers which are not captured by
nsIMsgDBHdr- such asList-ID:- as per nsIMsgDBHdr terms, filtering occurs during header parsing but relies on having the full, raw, header block passed into the filter code.
Check spam classification:
Check spam classification with server-side assistance (presumably standard systems like spamassassin don't work here, so does EWS provide spam hints in headers?)
For incoming-mail filters, check both before and after junk classification (it's a dropdown in the filter editor).
Check filter actions:
- set up cases for both header-only and full-body filters
- move message to other folder
- on same server
- to a local folder
- delete message
- tag message
- etc...
check that multiple filters and multiple actions trigger as expected:
- single filter with multiple actions (e.g. tag message then move to local folder)
- multiple matching filters (e.g. one filter which tags a message, and another which moves it to another folder).
| Reporter | ||
Updated•5 months ago
|
Description
•