Open
Bug 822047
Opened 11 years ago
Updated 2 years ago
Add tests for signature placement in message composition
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
NEW
People
(Reporter: rsx11m.pub, Unassigned)
References
Details
Attachments
(1 file)
3.89 KB,
patch
|
Details | Diff | Splinter Review |
There are currently no comprehensive automated unit tests for the signature position (specifically bug 57802, bug 273114, bug 545859 for mails created from the command line or another application; and bug 167319 for omitting or adding the signature on reply and forward actions) depending on the various reply/forward mode settings in the Composition & Addressing Account Settings. Covered are bug 58406 for suppressing the signature separator, and bug 566825 for switching signatures. Existing unit tests are mailnews/compose/test/unit/test_mailtoURL.js (xpcshell) for basic URL parsing and mozmill/composition/test-signature-updating.js for multiple signatures and separators (and a couple of recent regressions from the filelink effects on plain-text composition). I'd suggest to create a parallel test-signature-position.js Mozmill test to cover the remaing bugs in above list.
That's what I've started for testing signature placement for mailto: URLs in the different reply settings, coming up with 12 different cases. This won't work as test_mailtoURL.js doesn't actually create the message but only tests the parsing of the URL into individual components, but may serve as a starting point for a Mozmill test actually testing the nsIMsgCompose interface covering those cases.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•