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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1820 Actions

    Problem Report Number 1820
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0897
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-02-07 08:00
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 4.1.1
    Test Identification tset/XPROTO/staccsscnt 1
    Problem Summary TSD4W.00129 This test may fail on IUTs using an unbranded server that may not be configured to support access control requests from the client machine.
    Problem Text
    This test may fail on IUTs using an unbranded server that may not
    be configured to support access control requests from the client
    machine.

    When a client sends a valid SetAccessControl protocol request to the X server,
    then the X server does not send back an error, event or reply to the client.
    The X/Open CDE Components and Profile Definitions requires a test environment
    in which the X protocol driving the display is carried over an external
    TCP/IP connection. The test suite (client) does not reside on the same host
    as the X server, which results in an Access error for the SetAccessControl
    protocol request.

    Additional information:
    Because of the test environment (using an X Terminal for display), there is
    no way to configure the test system to grant permission for the remote client
    to perform a SetAccessControl request.

    The tests for XAddHost, XAddHosts, XRemoveHost and XRemoveHosts Xlib
    functions (which manipulate the host's access control list ) specifically
    test for a BadAccess return and flags the test as "Untested" when that
    occurs.

    However, the SetAccessControl testcase (which requires the same level of
    permission on the host in order to enable/disable the access control list)
    does not test for a BadAccess return code. Instead, when that occurs, it
    flags the test as "Failed." Since these tests are running in the same test
    environment, the SetAccessControl testcase is inconsistent with the
    aforementioned tests, which do not fail for the same test condition.

    Compare the SetAccessControl and XAddHost test assertions:

    SetAccessControl -
    >>ASSERTION A SetAccessControl-1
    When a client sends a valid SetAccessControl protocol
    request to the X server, then the X server does not send
    back an error, event or reply to the client.
    >>STRATEGY
    Call library function testfunc() to do the following:
    Open a connection to the X server using native byte sex.
    Send a valid SetAccessControl protocol request to the X server.
    Verify that the X server does not send back an error, event or reply.
    Open a connection to the X server using reversed byte sex.
    Send a valid SetAccessControl protocol request to the X server.
    Verify that the X server does not send back an error, event or reply.

    XAddHost -
    >>ASSERTION B XAddHost-1
    A call to XAddHost adds the specified host to the access
    control list for the display.
    >>STRATEGY
    Get current acl.
    If current list includes the host to be added:
    Remove host with XRemoveHost
    Get current acl.
    Check that host to be added is not in the list.
    Call XAddHost to add host.
    If call fails with a BadAccess:
    Report that assertion can not be tested from this host.
    Get new acl.
    Verify that host is in new acl.
    Test Output
    Test 1: FAIL
    Expect: wanted NOTHING, got ERROR - BadAccess
    Test SetAccessControl failed with 1 error.

    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