 |
|
|
|
Feature Test Spec
5.0 Project (Sea-Monkey)
Mail and News Component
Newsgroups:
Remove Expired Articles
Written by: Stacey Curtis
References:
UI Specification:
Other:
Approx. number of test cases: 10 (minimum)
Description: Removal of expired news messages. Message expiration is
performed by the server, but the client should properly identify these
messages and offer to remove them from the user's view on a newsgroup-specific
basis.
| . |
Test Cases |
Notes
|
Expected Outcome (if not obvious)
|
| 1 |
Display an expired article. |
I've had good luck with our internal news server "news" exipiring articles
on the comp.mail.imap and comp.mail.misc groups (try going to the earliest
postings to check), but you could also configure a news server yourself
to expire articles very soon for testing purposes. There may also be a
way to muck with this in the .newsrc...I'll check when I get a chance. |
The message should be displayed only as an indication that the article
has been expired and is no longer available for retrieval. There will probably
be a clickable option to "remove all expired articles." |
| 2 |
Remove all expired articles. |
See expected outcome in test above. Identify at least two expired messages. Don't always use the earliest possible expired message as the trigger to expire all messages. |
Clicking on the link or button should run the url "news://[server]/[group]?list-ids.
After it is run, the currently-viewed message should be deselected (a new
message might load), and no more messages in the group should be shown
as expired (check the second known expired message). Check to ensure that earlier messages as well as any later expired ones were removed, as there was apparently a problem with this in 4.x.
|
| . |
Secure Newsgroup |
Notes
|
Expected Outcome (if not obvious)
|
| 1 |
Test #1. |
. |
. |
| 2 |
Test #2. |
. |
. |
| . |
Password-protected Newsgroup |
Notes
|
Expected Outcome (if not obvious)
|
| 1 |
Test #1. |
. |
. |
| 2 |
Test #2. |
. |
. |
| . |
Sub-group |
Notes
|
Expected Outcome (if not obvious)
|
| 1 |
Test #1. |
. |
. |
| 2 |
Test #2. |
. |
. |
| . |
Various servers |
Notes
|
Expected Outcome (if not obvious)
|
| 1 |
Test #1. |
Test with as many different kinds of news servers as possible. |
. |
| 2 |
Test #2. |
. |
. |
|
|
|
