Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0848 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 0848.

Report 0848 Actions

    Problem Report Number 0848
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0363
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-01-09 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.5
    Test Identification POSIX.cmd/mailx 365, 366
    Problem Summary TSD4C.00148 This test may fail on implementations where mailx modifies a message's header after the message is read.
    Problem Text
    This test may fail on implementations where mailx modifies a
    message's header after the message is read.

    The test suite assumes that 365_2.out and 365_3.out are the same but
    on our implementation a 'Status: ' line is included in the header
    portion of each mail message and that status changes depending on
    the action taken (or not taken) when mailx is entered in Receive mode.
    Test cases 365 and 366 both fail for the same reason. That is,
    when mailx is invoked and a series of lines input to it the first
    new mailx message has the following status:
    mailx -n -f mailx_in /* mailx messages displayed and have no
    /* status yet: "n" new
    set toplines=4 /* no change to status
    save 1 365_1.out /* message 1 has not been read so the copy
    /* in 365_1.out will have status old "O"
    top 1 /* message 1 is read and now has status
    /* read "R"

    The test case continues by redirecting the output from awk into
    365_2.out. The awk script takes as input the results of the previous
    mailx commands (above) and prints out the 4 lines generated from
    the "top 1" command. This output contains, in its header section, a
    status line from Message 1 (AFTER it has been read by 'top'):
    Status: R

    The test case continues by generating an output file, for comparison,
    using the original output file, 365_1.out. However, the original,
    since it was never read, before it was saved, has a different status:
    Status: O

    Since header lines beyond "From " are not defined, it is implementation
    defined what an implementation includes in this header information.
    We believe that these two test cases should be changed so that the
    output files will be captured under the same circumstances so that
    they will be in the same state.
    Test Output
    **************************************************************
    /tset/POSIX.cmd/mailx/mailx_05.ex 1.Failed


    Test Information:
    Assertion #365 (C): Specification of mailx toplines var
    <LC> iable
    diff of "365_2.out" and "365_3.out":
    3c3
    < Status: R
    ---
    > Status: O
    Command failed: 'jrnl_file_diff 365_2.out 365_3.out'
    **************************************************************
    /tset/POSIX.cmd/mailx/mailx_05.ex 1.Failed


    Test Information:
    Assertion #366 (C): Default value for mailx toplines va
    <LC> riable is 5
    diff of "366_2.out" and "366_3.out":
    3c3
    < Status: R
    ---
    > Status: O
    Command failed: 'jrnl_file_diff 366_2.out 366_3.out'
    **************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree this is a test suite deficiency in the test
    suite version(s) listed.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority