Here is more detail regarding the UNIX/POSIX test return codes that I cited
earlier.  Perhaps this could help as you formalize the LTP test return
codes.

      PASS - a test result belonging to this group is considered to be a
      pass for compliance testing purposes:
            Pass - the test has been executed correctly and to completion
            without any kind of problem
            Warning - the functionality is acceptable, but you should be
            aware that later revisions of the relevant standards or
            specification may change the requirements in this area.
            FIP - additional information is provided which needs to be
            checked manually.
            Unsupported - an optional feature is not available or not
            supported in the implementation under test.
            Not in Use - some tests may not be required in certain test
            modes or when an interface can be implemented by a macro or
            function and there are two versions of the test only one is
            used.
            Untested - no test written to check a particular feature or an
            optional facility needed to perform a test is not available on
            the system.
      FAIL - a test result belonging to this group is considered to be a
      fail for compliance testing purposes (unless the failure has been
      waived by an agreed Problem Report in the Certification Problem
      Reporting database):
            Fail - the interface did not behave as expected.
            Uninitiated - the particular test in question did not start to
            execute.
            Unresolved - the test started but did not reach the point where
            the test was able to report success or failure.
            Unreported - a major error occurred during the testset
            execution.

http://www.linux-foundation.org/test/lsb-runtime-test-faq.html#FIPS

In /opt/ltp/include/test.h, TPASS and the other test return codes are
defined for LTP; however, I noticed they are number as 2^n.   Were these
codes intended to be masked (eg., TFAIL|TBROK)?

George (gk4)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to