|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2233 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 2233.
Report 2233 Actions
Problem Report Number 2233 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1148 Raised 2001-12-21 08:00 Updated 2003-03-13 08:00 Published 2001-12-24 08:00 Product Standard Motif Toolkit Certification Program The Open Brand certification program Test Suite VSM version 4.1.3 Test Identification Widgets/XmCommandError 1 Problem Summary TSD4M.00055 Im running vsm version 4.1.3A on Unix Tru64 X5.1 (running with Motif version 1.2) Im getting failure on test case "XmCommandError" However, on the same machine, with the same configuration, if I use v... Problem Text
Im running vsm version 4.1.3A on Unix Tru64 X5.1
(running with Motif version 1.2)
Im getting failure on test case "XmCommandError"
However, on the same machine, with the same configuration, if I
use vsm version V4.1.2, this test case in successful.
I compared the source code of V4.1.2 and V4.1.3A to discover one
change in file "/vsm4/tset/funcs/cmderror.c" that I feel may
have something to do with the failure. I could say this
because I modified this source file in V4.1.3A as in V4.1.2, ran the
test suite on this particular test case to obtain a positive
result. The only change in the file I see there is the function
"mvsExpect1MoreCallback" being moved up a few lines in code. In
other words, the function is called a little earlier in 4.1.3A code.
Im interested to know the reason for doing that.
There is one more observation made. Earlier results of running vsm4.1.2
on a machine running with Motif 2.1 also show failure on case
"XmCommandError".
What we could infer from this is that the file "cmderror.c" was
probably changed in order to get the test case "XmCommandError"
right when system is running with Motif 2.1, but this change
might possibly be causing the test case to fail in systems running
with Motif 1.2
So, we believe that the test case failure on "XmCommandError" that we
are getting is due to "test suite deficiency" and not due to the
motif product that we are using.
We recommend a check be added in the source code so as to distinguish
systems running with Motif 2.1 from those running with Motif 2.1, add
appropriate code for both the cases so that we could get the test
case "XmCommandError" right for either of the Motif versions, the
system is running with.Test Output
Below is the description of failure as seen in the journal file:
..................
A call to void XmCommandError(Widget widget, XmString
error) displays the message specified by error in the
history area of the Command widget specified by widget.
ERROR: Didn't receive expected callback(s) XmNfocusCallb
ack of widget XmCommand of class xmCommandWidgetClass. Received 0,
Expected 1
ERROR: Received unexpected callback(s) XmNfocusCallback
of widget XmCommand of class xmCommandWidgetClass Received 1, Expected 0
TEST: Add a second error message using XmCommandError.
TEST: Add a third error message using XmCommandError.
......................Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
A test suite deficiency is recommended
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:
- View Report 2233
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority