Ignore:
Timestamp:
Feb 25, 2011, 9:26:54 PM (13 years ago)
Author:
Bruno Cornec
Message:
  • Update mindi-busybox to 1.18.3 to avoid problems with the tar command which is now failing on recent versions with busybox 1.7.3
File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2.2.9/mindi-busybox/testsuite/README

    r902 r2725  
    1 Update: doesn't work as described. Try "make check" from parent dir...
    2 * * *
    3 
    41To run the test suite, change to this directory and run "./runtest".  It will
    52run all of the test cases, and list those with unexpected outcomes.  Adding the
    63-v option will cause it to show expected outcomes as well.  To only run the test
    7 cases for particular applets, specify them as parameters to runtest.
     4cases for particular applets:
    85
    9 The test cases for an applet reside in the subdirectory of the applet name.  The
    10 name of the test case should be the assertion that is tested.  The test case
    11 should be a shell fragment that returns successfully if the test case passes,
    12 and unsuccessfully otherwise.
     6./runtest <applet1> <applet2>...
     7
     8Set SKIP_KNOWN_BUGS environment variable to any non-empty value
     9to exclude tests which are known to fail.
     10
     11Set SKIP_INTERNET_TESTS to exclude tests which require working
     12internet connection.
     13
     14
     15Common causes of false positives:
     16
     17For busybox built against uclibc, /etc/TZ does not exist or does not match
     18host system timezone setting. For glibc based host systems, timezone settings
     19are in /etc/localtime.
     20
     21LANG and LC_xxx environment variables set to non-C locale.
     22
     23
     24Developer's notes:
     25
     26The test cases for an applet reside in the subdirectory of the applet name.
     27The name of the test case should be the assertion that is tested.
     28The test case should be a shell fragment that returns successfully
     29if the test case passes, and unsuccessfully otherwise.
    1330
    1431If the test case relies on a certain feature, it should include the string
    1532"FEATURE: " followed by the name of the feature in a comment.  If it is always
    1633expected to fail, it should include the string "XFAIL" in a comment.
     34
    1735
    1836For the entire testsuite, the copyright is as follows:
Note: See TracChangeset for help on using the changeset viewer.