Once the command-line tools have been tested, the email gateway and cgi gateway may be tested independently, as neither depends on the other for functionality.
This test case addresses EMAIL-GATEWAY.FR1 through EMAIL-GATEWAY.FR7
Command-line tool testing must be complete
Table 2-11. Test script: EMAIL-GATEWAY.TC
| User actions | System Response/User examination |
| Install the email gateway with a test repository containing the test_data directory's good_template template as the defect template, and both sample_defect_1 and sample_defect_2 as two sample defects | |
| Mail the email gateway with a garbage subject line | System should return a message containing the email gateway's help text |
| Run through the CAT.TC tests by sending the gateway email messages with subject lines corresponding to those in the CAT.TC tests | System should return mail messages with appropriate feedback |
| Run through the QUERY.TC tests by sending the gateway email messages with subject lines corresponding to those in the QUERY.TC tests | System should return mail messages with appropriate feedback |
| Email the gateway a message with the subject line "request-blank-template defect" | System should return a mail message containing in the body a blank defect entry with default values filled in |
| Edit the text returned by the "request-blank-template" message, editing it as a new issue, and send that message back to the email gateway with the subject line "file" | System should file the message and return a feedback message containing the resultant ID. Use the "cat" command through the gateway to ensure that the new issue was filed correctly. |