circuitpython/tests
Jeff Epler 100de9e5b9
add a script to make it easy to endorse test output
Invoke it on the "out" file and it's moved to the correct "exp" file,
ready to git add & git commit.
2023-08-18 12:50:06 -05:00
..
basics endorse new test output 2023-08-15 11:58:19 -05:00
circuitpython document EnvelopeState 2023-07-20 16:26:07 -05:00
circuitpython-manual synthio: update ring mod manual test 2023-05-30 19:32:24 -05:00
cmdline py/compile: Allow new qstrs to be allocated at all compiler passes. 2022-05-17 23:39:22 +10:00
cpydiff initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
extmod asyncio test fixes and asyncio library updates 2023-08-18 13:16:16 -04:00
feature_check remove lib from exludes, fix all remaining typos 2023-03-23 13:59:08 +07:00
float initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
import run updated pre-commit 2023-02-01 13:38:41 +05:30
inlineasm initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
internal_bench Merge MicroPython 1.12 into CircuitPython 2021-05-03 14:01:18 -07:00
io Merge tag 'v1.18' 2022-02-15 12:36:26 -06:00
jni Merge MicroPython v1.15 into CircuitPython 2021-05-12 17:51:42 -07:00
micropython Skip the import_mpy_native_gc test, it is known to be broken 2023-08-18 12:50:05 -05:00
misc remove lib from exludes, fix all remaining typos 2023-03-23 13:59:08 +07:00
perf_bench initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
stress initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
testlib Add some more Note tests 2023-05-24 10:00:12 -05:00
thread initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
unicode run updated pre-commit 2023-02-01 13:38:41 +05:30
unix Re-add usercmodule sources & endorse new extra_coverage output 2023-08-18 12:50:03 -05:00
vectorio remove unused import 2022-03-19 11:36:23 -05:00
README tests: Rename run-tests to run-tests.py for consistency. 2021-03-12 19:56:09 +11:00
endorse.py add a script to make it easy to endorse test output 2023-08-18 12:50:06 -05:00
pyboard.py countio: add selectable rise and fall detection, pulls 2021-12-31 16:34:58 -05:00
run-internalbench.py run updated pre-commit 2023-02-01 13:38:41 +05:30
run-multitests.py tests/run-multitests.py: Read IP address from boot nic if available. 2022-06-03 14:35:37 +10:00
run-natmodtests.py Fix all natmod tests to run on x64 2022-02-13 11:18:38 -06:00
run-perfbench-table.py initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
run-perfbench.py Fix .bin, .hex and .uf2 with new linker sections 2023-03-20 14:02:57 -07:00
run-tests-exp.py Merge MicroPython v1.15 into CircuitPython 2021-05-12 17:51:42 -07:00
run-tests-exp.sh tests: Rename run-tests to run-tests.py for consistency. 2021-03-12 19:56:09 +11:00
run-tests.py initial v1.19.1 merge; not compiled yet 2023-08-01 13:50:05 -04:00
skip_if.py run code formatting script 2021-03-15 19:27:36 +05:30

README

This directory contains tests for various functionality areas of MicroPython.
To run all stable tests, run "run-tests.py" script in this directory.

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.py 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.py script uses small scripts in the
feature_check directory to check whether each such feature is present,
and skips the relevant tests if not.

Tests are generally verified by running the test both in MicroPython and
in CPython and comparing the outputs. If the output differs the test fails
and the outputs are saved in a .out and a .exp file respectively.
For tests that cannot be run in CPython, for example because they use
the machine module, a .exp file can be provided next to the test's .py
file. A convenient way to generate that is to run the test, let it fail
(because CPython cannot run it) and then copy the .out file (but not
before checking it manually!)

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
module, should go in the import/ subdirectory.