Boost logo

Boost :

From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2004-09-27 04:55:20


Gennadiy Rozental writes:
> Could you please point me to docs that describe how to mark test as
> expected failure.

To mark a number of test case failures on a number of particular
toolsets as "expected", you add an entry to
"status/explicit-failures-markup.xml" along the following lines:

    <!-- test -->
    <library name="test">

        <mark-expected-failures>
            <test name="test_case1"/>
            <test name="test_case2"/>
            ...
            <toolset name="toolset1"/>
            <toolset name="toolset2"/>
            ...
            <note author="Gennadiy Rozental">
                This failure is due to Reason #1.
            </note>
        </mark-expected-failures>

        <mark-expected-failures>
            <test name="test_case7"/>
            <test name="test_case9"/>
            ...
            <toolset name="toolset1"/>
            <toolset name="toolset5"/>
            ...
            <note author="Gennadiy Rozental">
                This failure is due to Reason #2.
            </note>
        </mark-expected-failures>

        ...

    </library>

Then you validate the modified XML following the instructions at the
very top of the file:

    The following online services can be used to validate your changes
    to this file:
                                                                                                                
        - http://apps.gotdotnet.com/xmltools/xsdvalidator/
                                                                                                                
     When using the gotdotnet tool you need to provide both the
     explicit-failures-markup.xml file as the XML document and the
     explicit-failures.xsd as the schema document. Use the browse
     buttons to select them from your local hard drive.

... and if everything is OK, check it in. That's it.

HTH,

-- 
Aleksey Gurtovoy
MetaCommunications Engineering

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk