djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

tests/README: Explain how tests get skipped

Browse Source
This commit is contained in:
Tom Soulanille 2015-09-15 09:48:56 -07:00 committed by Paul Sokolovsky
parent 0d6b2341b8
commit 04fffe6562
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
tests/README
View File

@ -1,7 +1,17 @@
This directory contains tests for various functionality areas of MicroPython. This directory contains tests for various functionality areas of MicroPython.
To run all stable tests, run "run-tests" script in this directory. Note To run all stable tests, run "run-tests" script in this directory.
that bytecode tests are not yet stable and should be run separately in
"bytecode" subdirectory. Tests of capabilities not supported on all platforms should be written
to check for the capability being present. If it is not, the test
should merely output 'SKIP' followed by the line terminator, and call
sys.exit() to raise SystemExit, instead of attempting to test the
missing capability. The testing framework (run-tests in this
directory, test_main.c in qemu_arm) recognizes this as a skipped test.
There are a few features for which this mechanism cannot be used to
condition a test. The run-tests script uses small scripts in the
feature_check directory to check whether each such feature is present,
and skips the relevant tests if not.
When creating new tests, anything that relies on float support should go in the When creating new tests, anything that relies on float support should go in the
float/ subdirectory. Anything that relies on import x, where x is not a built-in float/ subdirectory. Anything that relies on import x, where x is not a built-in