micropython/tests
Damien George 709136e844 tests/basics: Use str.format instead of % for formatting messages.
Only use % formatting when testing % itself, because only str.format is
guaranteed to be available on any port.
2019-10-29 22:22:37 +11:00
..
basics tests/basics: Use str.format instead of % for formatting messages. 2019-10-29 22:22:37 +11:00
cmdline
cpydiff
extmod extmod/vfs: Rename BP_IOCTL_xxx constants to MP_BLOCKDEV_IOCTL_xxx. 2019-10-29 14:17:29 +11:00
feature_check
float tests: Rename "array" module to "uarray". 2019-10-22 19:16:54 +11:00
import
inlineasm tests: Rename "array" module to "uarray". 2019-10-22 19:16:54 +11:00
internal_bench
io
jni
micropython tests: Rename "array" module to "uarray". 2019-10-22 19:16:54 +11:00
misc tests: Rename "array" module to "uarray". 2019-10-22 19:16:54 +11:00
net_hosted
net_inet
perf_bench
pyb
pybnative
qemu-arm
stress
thread
unicode
unix
wipy
README
run-internalbench.py
run-perfbench.py
run-tests
run-tests-exp.py
run-tests-exp.sh

README

This directory contains tests for various functionality areas of MicroPython.
To run all stable tests, run "run-tests" 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 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
float/ subdirectory.  Anything that relies on import x, where x is not a built-in
module, should go in the import/ subdirectory.