TEST CASE REPORT
WEEK ENDING MM/DD
COMPANY:
TEST CASE |
DATE |
PASS/FAIL |
COMMENTS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instructions:
- This report is to be completed each Friday for the duration of the trial and sent to Dick Dowd by close of business.
- Should a test case be run multiple times by a carrier, each case should be reported. For example, if 4.5.1.1.10 test case is called to three carriers by the author of this report, it should be indicated so - using a, b, c, or something similar.
- If the test case fails, but is corrected and then passed, indicate the test passed, however, note in comments the reason for the original failure.
- A "P" or "F" are the appropriate values for the pass/fail column.
- This report will be summarized each week by Dick Dowd and sent to the industry participants, and placed on ported.com.
- At the end of the trial, the weekly reports will be summarized for the FCC report. The failures will not name specific companies.