Skip to content

Commit 04fffe6

Browse files
pramasoulpfalcon
authored andcommitted
tests/README: Explain how tests get skipped
1 parent 0d6b234 commit 04fffe6

1 file changed

Lines changed: 13 additions & 3 deletions

File tree

tests/README

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,17 @@
11
This directory contains tests for various functionality areas of MicroPython.
2-
To run all stable tests, run "run-tests" script in this directory. Note
3-
that bytecode tests are not yet stable and should be run separately in
4-
"bytecode" subdirectory.
2+
To run all stable tests, run "run-tests" script in this directory.
3+
4+
Tests of capabilities not supported on all platforms should be written
5+
to check for the capability being present. If it is not, the test
6+
should merely output 'SKIP' followed by the line terminator, and call
7+
sys.exit() to raise SystemExit, instead of attempting to test the
8+
missing capability. The testing framework (run-tests in this
9+
directory, test_main.c in qemu_arm) recognizes this as a skipped test.
10+
11+
There are a few features for which this mechanism cannot be used to
12+
condition a test. The run-tests script uses small scripts in the
13+
feature_check directory to check whether each such feature is present,
14+
and skips the relevant tests if not.
515

616
When creating new tests, anything that relies on float support should go in the
717
float/ subdirectory. Anything that relies on import x, where x is not a built-in

0 commit comments

Comments
 (0)