circuitpython/tests
Jeff Epler cc16bd3d53
do not chain exceptions to themselves
cpython actually makes sure the newly chained exception doesn't create
a cycle (even indirectly); see _PyErr_SetObject use of "Floyd's cycle
detection algo". We'll go for the simpler solution of just checking
one level deep until it's clear we need to do more.

Closes: #7414
2023-01-04 08:40:20 -06:00
..
basics Chain exceptions while unwinding 2022-11-13 19:53:23 -06:00
circuitpython do not chain exceptions to themselves 2023-01-04 08:40:20 -06:00
circuitpython-manual Refactor dotenv module so that it can be tested on host 2022-10-04 09:51:27 -05:00
cmdline py/showbc: Print unary-op string when dumping bytecode. 2021-11-19 17:05:40 +11:00
cpydiff Merge tag 'v1.18' 2022-02-15 12:36:26 -06:00
extmod extmod/uasyncio/task.py: Fix crash when non-awaited task is awaited. 2022-10-15 14:58:07 -05:00
feature_check Merge tag 'v1.17' into merge-1.17 2021-10-15 08:20:54 -05:00
float py/formatfloat: Format all whole-number floats exactly. 2022-08-09 13:43:47 -04:00
import update to py tests and scripts due to black 22.1.0 2022-01-29 17:14:01 -05:00
inlineasm Merge MicroPython 1.12 into CircuitPython 2021-05-03 14:01:18 -07: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 fix test that used MpyError 2022-10-09 20:27:39 -04:00
misc Merge tag 'v1.18' 2022-02-15 12:36:26 -06:00
perf_bench Merge tag 'v1.18' 2022-02-15 12:36:26 -06:00
pybnative tests/pybnative: Make while.py test run on boards without pyb.delay. 2021-09-01 00:43:41 +10:00
qemu-arm Merge MicroPython 1.12 into CircuitPython 2021-05-03 14:01:18 -07:00
stress Merge MicroPython 1.12 into CircuitPython 2021-05-03 14:01:18 -07:00
thread Merge tag 'v1.16' 2021-06-18 10:54:19 -05:00
unicode Fix unicode test 2021-08-17 18:18:46 -07:00
unix update expected result 2022-12-08 15:39:19 -06:00
vectorio remove unused import 2022-03-19 11:36:23 -05:00
pyboard.py countio: add selectable rise and fall detection, pulls 2021-12-31 16:34:58 -05:00
README tests: Rename run-tests to run-tests.py for consistency. 2021-03-12 19:56:09 +11:00
run-internalbench.py tests: Rename run-tests to run-tests.py for consistency. 2021-03-12 19:56:09 +11:00
run-multitests.py tests/run-multitests.py: Add broadcast and wait facility. 2021-08-13 23:26:34 +10:00
run-natmodtests.py Fix all natmod tests to run on x64 2022-02-13 11:18:38 -06:00
run-perfbench.py update to py tests and scripts due to black 22.1.0 2022-01-29 17:14:01 -05: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 Implement chained exceptions 2022-11-13 19:52:50 -06:00
skip_if.py run code formatting script 2021-03-15 19:27:36 +05:30

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.