You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

You are here: Mozilla MailNews Functional / UI Tests > Message Filters: Custom Headers

Feature Test Spec: Mail and News Component

Mail and News Component: Message Filters: Custom Headers

Written by Laurel Carlson

Feature description

Simple user interface to allow users to search or filter based on any header. Feature currently not available for news.

References:

No current UI or design specs available on mozilla.org
Main Feature bug: https://bugzilla.mozilla.org/show_bug.cgi?id=16902

Some of the custom header bugs reported in moz1.0/netscape7.0

  1. Custom Header Dialog - basic UI:
    1. Accessible from criteria dropdown:
      1. from Filter Rules dialog
      2. from Search Messages dialog
    2. Add button
    3. Remove button
    4. Text field for header name
    5. List box for headers
    6. Tabbing/keyboard access to fields
    7. General Cancel/OK
  2. Add header
    1. single
    2. multiple
    3. limit for number of headers in list? currently we have no limit, but greater than 50 will cause problems -- should warn. Ref: bug 104085
    4. headers with non alphabetic characters:
      1. dashes ( like Reply-To)
    5. invalid characters: currently can cause problems, but no handling -- see bug 107620, 155496
      1. colon
      2. control characters
      3. spaces?
    6. headers appear properly in Custom Headers dialog list
      1. appears in custom headers dialog accessed through search ui
      2. appears in custom headers dialog when accessed through filter ui
      3. appears immediately
      4. changes to custom headers is written to prefs.js and/or rules.dat on confirm - if crash occurs, changes already written to file
      5. preserved through exit:
        • check the ui
        • check the list in prefs.js (mailnews.customHeaders)
    7. headers appear in Filter Rules criteria dropdown after adding
      1. for mail selection in filter dialog
      2. Not available for News - filtering not implemented for news (bug 17483, bug 16913)
    8. headers appear in Search Messages criteria dropdown after adding
    9. cancel addition
    10. Add valid headers:
    11. Add invalid headers -- no error checking here
    12. add header doesn't disrupt existing criteria selection in Filter dialog
      1. selected filter criteria is mail/not a custom header
      2. selected filter criteria is mail/custom header
    13. add header doesn't disrupt existing criteria selection in Search dialog
      1. selected search criteria is mail/not a custom header
      2. selected search criteria is mail/custom header
  3. Edit/replace existing header: current design provides for only Add/Remove, no Edit.
  4. Delete header
    1. single
    2. multiple
    3. Delete last/only header in list
    4. Add one and delete it
    5. Deletions to custom headers list appear properly
      1. change appears in custom headers dialog accessed through search ui
      2. change appears in custom headers dialog when accessed through filter ui
      3. change appears immediately
      4. change preserved through exit
    6. cancel deletion
    7. delete a header which has an associated filter -- not sure of how we handle, make sure it's sensible
  5. Filter for Custom Header
    1. Filter folders various version mail servers
      1. online
      2. offline
    2. Filter for valid header
    3. Filter for invalid header -- simple no match, no validation of header/error checking
    4. Filter with valid matches
    5. Filter with no matches (valid header)
    6. Filter multiple headers
      1. multiple AND
      2. multiple OR
      3. mix of custom header criteria and regular header criteria
  6. Search for Custom Header
    1. Search various version mail servers
      1. Search locally
        • online
        • offline
      2. Search server
    2. Search for valid header
    3. Search for invalid header -- simple no match, no validation of header/error checking
    4. Search with valid matches
    5. Search with no matches (valid header)
    6. Search multiple headers
      1. multiple AND
      2. multiple OR
      3. mix of custom header search criteria and regular search header criteria
  7. Other/Misc tests:
    1. Try to edit custom header simultaneously accessed from filter and search dialog:
      1. add
      2. delete
      3. edit/replace
    2. Case where rules.dat has custom headers defined, but not defined in prefs.js (if someone has copied rules.dat from other profile) -- ref: bug 141354
      1. the custom headers which are called in rules.dat should automatically be added to prefs.js
      2. adding new filters should not cause any rules.dat corruption
      3. custom headers should be retained in rules.dat, prefs.js, ui through exit
    3. ??? remember to bring up case for checking to see if header is even in a message when doing "doesn't contain". Not sure the design intention here, but in 4.5 (searching, maybe headers too) returns all messages in scope if doesn't contain is used. In other words, matches for the doesn't contain show in results even though those results/messages do not have the specified header.