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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0627 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 0627.

Report 0627 Actions

    Problem Report Number 0627
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0231
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.4
    Test Identification POSIX.cmd/ed
    50 55 113 162 179 181 213 305 315 318 359 487 504 507 508 563 633 634
    641 644 646
    Problem Summary PG4C.00045 The expected output for each of the test-cases mentioned
    aboved is wrong and need to be rectified.
    Problem Text The expected output for each of the test-cases mentioned aboved
    is
    wrong and need to be rectified.
    Test Output #50,#55: This is a test suite failure. The %% should have been
    escaped
    with a backslack() to prevent it from being
    interpreted
    by shell.

    #113 : This is a test suite failure. The test-suite tries to
    print
    all patterns matching starting from [a-z] and ending
    with [a-z]
    but not a digit.

    #162 : This is a test suite failre. Here the test case is trying
    to match all alphabetic characters [a-z] and any
    occurances
    of these alphabets to the end of the line. This will not
    match any digits at the end of the line.

    #179 : This is a test suite problem. The test-case is
    using expect, sleep to perform the test. This is
    silimar to the vuser. This is causing problems.

    #181 : The ".=" command (not .$) command should print the
    currenly addressed line in the buffer. The
    expected
    output is wrong. The expected output checks
    for "10"
    whereas the output obtained is "2" which is
    correct.


    #213 : This is a test suite failure. The 'c' or change command
    must be
    given an operant.

    #305 : Test suite problem. The test suite tests both the g and
    s command.
    The test case incorrectly tries to search for strings
    matching and
    ending with characters in the range [a-z].

    #315 : The test-case expects input form the user interactively,
    since the user is not available when the test-case is
    run,
    the "expect and send" combinations are used to simulate
    a user giving commands interactively. This test-case
    is failing since the time at which the input is given
    by the "expect and send" combinations is not within
    the expected time (this being system dependent).


    #318 : The test-suite tries to marks all lines having the
    contents of
    length256 and then later substitutes it with "MATCH".
    But
    the contents of length256 is more than 255 characters.
    Therefore
    the test-fails.

    #359 : test suite problem.
    Changing the input file
    from : 1,$G/[a-z]*$/
    to : 1,$G/[a-z].*$/

    and

    changing
    from s/[a-z]*$/MATCH/
    to s/$/MATCH/

    solves the problem.


    #487 : Test suite failure. Changing the input file
    from 1s/[a-z]*$/MATCH/
    to 1s/[a-z].*$/MATCH/


    #504 : Test suite failure. The //// should be changed to /////
    before the &.

    #507 : Test suite failure. The 2s/else/%%/
    should be replaced
    with 2s/else/\%\%/
    to check for % substitution.

    #508 : Test suite failure.
    need to change
    from : 2s/else/\\%%/

    to : 2s/else/\\\%\%/


    #563 : The test-suite fails. Changing the input file
    form 1,$v/[a-z]*$/ s/.*/MATCH/
    to 1,$v/[a-z].*$/ s/.*/MATCH/ should pass
    the test.

    #633 : Test-suite failure. Changing the input file
    from "w !cat"
    to "w"
    "!cat" should solve the problem.

    #641 : Test suite failure. The test first deletes one line.
    After deletion of the first line, the address
    of the
    current line is still "1". The expected
    output checks
    for "3" which is wrong.

    #644,#646 : The test-suite tries to echo the name of the file
    using
    the "%" symbol. The "%" should be escaped to mask its
    special meaning.
    The test should change
    "!echo %% %%
    "
    to "!echo \%\% \%\%
    "

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response We recommend this request be refused.

    The interpretation request does not provide journal output.

    Each interpretation must be filed for a single reason. It may
    contain references to many tests cases and/or test purposes,
    there can only be one reason for the request.

    We agree test purposes 179 and 315 may fail due to timing
    problems.

    We believe tests 504, 507, 508, 641, 644, and 646 fail on the
    IUT because the shell does not properly interpret complex
    backslash
    removal rules. These tests are not testing any backslash
    removal
    assertions and have rewritten them to be simplier and clearer in
    4.1.5. But the tests in 4.1.4 should still pass on conforming
    systems.

    We believe all the other tests are correct and should pass on
    conforming
    IUTs.

    #50, #55
    Our opinion differs.

    The shell does not normally expand % characters. %% is
    only
    meaningful in ${%%:...} constructs, which clearly does
    not
    apply here.

    Assertion 55 does not even contain a %% sequence.

    #113
    Our opinion differs.

    No [a-z] patterns are used in test.

    #162
    Our opinion differs.

    No [a-z] patterns are used in test.

    #179
    Expect script has been updated to use new libraries to
    avoid
    potential timing problems.

    #181
    Our opinion differs.

    No .$ patterns are used in test.

    #213
    Our opinion differs.

    Assertion uses:
    1,2c
    .
    which is correct.

    #305
    Our opinion differs.

    No [a-z] patterns are used in test.

    #318
    Our opinion differs.

    XBD states:
    The implementation will support any regular
    expression
    that does not exceed 256 bytes in length.

    Since the implementation must support regular
    expressions that
    to not exceed then XCU4 requires ed to match patterns of
    at least
    256 characters.

    Systems which fail on patterns of length 255 are
    non-conformant.

    #359
    Our opinion differs.

    [a-z]*$ matches 0 or more occurences of a lower case
    ACSII
    character at the end of a line, which is what the test
    requires.
    [a-z].*$ would match any line with a lower case letter
    in it and
    s/$/NATCH/ would simply put a MATCH at the end of exery
    line. This
    is clearly wrong for our test purposes.

    #487
    Our opinion differs.

    [a-z]*$ matches 0 or more occurences of a lower case
    ACSII
    character at the end of a line, which is what the test
    requires.
    [a-z].*$ would match any line with a lower case letter
    in it.

    #504
    Test has been simplified eliminate removal confusion.

    #507
    Test has been simplified eliminate removal confusion.

    #508
    Test has been simplified eliminate removal confusion.

    #563
    Our opinion differs.

    [a-z]*$ matches 0 or more occurences of a lower case
    ACSII
    character at the end of a line, which is what the test
    requires.
    [a-z].*$ would match any line with a lower case letter
    in it.

    #633
    Our opinion differs.

    XCU4 states:
    If file begins with !, the rest of the line will
    be
    taken to be a shell command line whose standard
    input will be the addressed lines. Such a shell
    command line will not be remembered as the
    current
    pathname.

    "w !cat" tests the assertion exactly. No other
    construct
    will do here...

    #641
    Our opinion differs.

    XCU4's synopsis for ed's = command is:

    Synopsis: ($)=

    Meaning: if no address is given then use $ as the
    address.
    In the case of this test $ (being the last line of the
    buffer) is
    3 and this is what we test for...

    #644
    Test has been simplified eliminate removal confusion.
    #646
    Test has been simplified eliminate removal confusion.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority