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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1808 Actions

    Problem Report Number 1808
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0885
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1997-02-06 08:00
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.0.0
    Test Identification Xt11/tstvalues 5
    Problem Summary TSD4W.00141 This test may fail on all implementations because the tested events are never set.
    Problem Text
    Similar case: XtVaSetValues-5 in Xt11/tvastvals.

    This failure results because the SetValues function of set_values field
    of avsformWidgetClass/avsform2WidgetClass/avsform3WidgetClass are (defined
    respectively in AvsForm.c/AvsForm2.c/AvsForm3.c as below) the same. The test
    does not do any constraint modification.

    /* ARGSUSED */
    static Boolean SetValues(current, request, new)
    Widget current, request, new;
    {
    return( FALSE );
    }

    The above function will be recursively called by CallSetValues and
    CallConstraintSetValues functions in SetValues.c, CallSetValues and
    CallConstraintSetValues functions will be called by XtSetValues or
    XtVaSetValues function. The code in XtSetValues function is:

    /* Inform widget of changes, then inform parent of changes */
    redisplay = CallSetValues (wc, oldw, reqw, w, args, num_args);
    if (hasConstraints) {
    redisplay |= CallConstraintSetValues(cwc, oldw, reqw, w, args, num_args)
    ;
    }

    After the current widget's constraint(s) are setup, XtSetValues uses
    "static Boolean SetValues(...)" function to set the current widget's
    parent' constraint(s), but because the SetValues function just executes a
    "return(FALSE)" call and does not modify any constraints, the test case fails.

    Test Output

    TEST CASE: XtSetValues

    TEST PURPOSE #5
    Assertion XtSetValues-5.(A)
    When the class of the specified widget's parent is a
    subclass of constraintWidgetClass a call to void
    XtSetValues(object, args, num_args) shall call the
    constraint set_values procedures from constraintWidgetClass
    on down to the parent's class, passing to them the specified
    widget as an argument.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create avsform widget in boxw1 widget
    PREP: Create avsform2 widget in avsform widget
    PREP: Create windows for widgets and map them
    PREP: Set constraint resource values for pushb_good widget
    TEST: set_values procedure two levels up was invoked first
    ERROR: Expected procedure invocation to be #1, is #0
    TEST: set_values procedure of parent was invoked second
    ERROR: Expected procedure invocation to be #2, is #0
    5 FAIL

    TEST PURPOSE #5
    Assertion XtVaSetValues-5.(A)
    When the class of the specified widget's parent is a
    subclass of constraintWidgetClass a call to void
    XtVaSetValues(object,...) shall call the constraint
    set_values procedures from constraintWidgetClass on down to
    the parent's class, passing to them the specified widget as
    an argument.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create avsform widget in boxw1 widget
    PREP: Create avsform2 widget in avsform widget
    PREP: Create windows for widgets and map them
    PREP: Set constraint resource values for pushb_good widget
    TEST: set_values procedure two levels up was invoked first
    ERROR: Expected procedure invocation to be #1, is #0
    TEST: set_values procedure of parent was invoked second
    ERROR: Expected procedure invocation to be #2, is #0
    5 FAIL


    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