micropython/tests
Damien George 571295d090 tests/extmod/ujson_dump_iobase.py: Return number of bytes written.
Otherwise returning None indicates that the write would block and nothing
was actually written.  Fixes issue #3990.
2018-07-30 12:05:48 +10:00
..
basics py/objgenerator: Implement __name__ with normal fun attr accessor code. 2018-07-10 16:33:57 +10:00
bench
cmdline
cpydiff
extmod tests/extmod/ujson_dump_iobase.py: Return number of bytes written. 2018-07-30 12:05:48 +10:00
feature_check
float py/lexer: Add support for underscores in numeric literals. 2018-06-12 12:17:43 +10:00
import tests/import: Add test for importing invalid .mpy file. 2018-06-18 17:50:34 +10:00
inlineasm
io tests: Move non-filesystem io tests to basics dir with io_ prefix. 2018-06-27 16:55:05 +10:00
jni
micropython
misc tests: Add tests using "file" argument in print and sys.print_exception. 2018-06-20 16:08:25 +10:00
net_hosted
net_inet
pyb tests/pyb: Make i2c and pyb1 pyboard tests run again. 2018-06-08 13:00:27 +10:00
pybnative
stress
thread
unicode
unix tests/unix/extra_coverage: Don't test stream objs with NULL write fun. 2018-06-18 12:35:56 +10:00
wipy
README
pyboard.py
run-bench-tests
run-tests tests/run-tests: Improve crash reporting when running on remote targets. 2018-07-20 09:27:28 +10:00
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.