micropython/tests
Damien George 0891cf7d2d tests: Disable for_range.py test for native emitter (it requires yield). 2015-12-08 21:39:21 +00:00
..
basics py: Don't try to optimise for+range when args are not simple expressions. 2015-12-08 21:05:14 +00:00
bench
cmdline
extmod extmod/modure: Make sure that errors in regexps are caught early. 2015-11-01 00:38:22 +03:00
feature_check tests: Actuall add feature check for complex type being available. 2015-12-06 15:13:26 +02:00
float tests/float/string_format: Add testcase for incorrect rounding for %f. 2015-11-22 18:08:49 +02:00
import
inlineasm py: In inline asm, vldr and vstr offsets now in bytes not words. 2015-10-31 10:50:45 +00:00
io
jni tests/jni: Add test for working with container of List interface. 2015-11-13 01:33:09 +02:00
micropython tests: Add more tests for viper 16/32-bit load/store, and ellipsis. 2015-10-13 18:24:36 +01:00
misc
pyb stmhal: Make uart.write() function correctly for timeout=0. 2015-11-30 17:29:52 +00:00
pybnative
unicode
unix tests/extra_coverage: Update for sys.modules addition. 2015-12-05 00:13:29 +02:00
wipy cc3200: Unmount all user file systems after a soft reset. 2015-11-16 23:43:47 +01:00
README
pyboard.py
run-bench-tests
run-tests tests: Disable for_range.py test for native emitter (it requires yield). 2015-12-08 21:39:21 +00: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.