micropython/tests
Paul Sokolovsky b565c36963 tests/object_new: Better messages, check user __new__() method.
Make messages more verbose and easier to follow and check that user class'
__new__() is not called by object.__new__(user_class).
2017-08-30 21:29:23 +03:00
..
basics tests/object_new: Better messages, check user __new__() method. 2017-08-30 21:29:23 +03:00
bench
cmdline
cpydiff
extmod extmod/modubinascii: Rewrite mod_binascii_a2b_base64. 2017-08-17 09:25:51 +03:00
feature_check
float
import
inlineasm
io py/stream: seek: Consistently handle negative offset for SEEK_SET. 2017-08-20 22:02:41 +03:00
jni
micropython
misc
net_hosted extmod/modussl_mbedtls.c: Add ussl.getpeercert() method. 2017-08-16 15:01:00 +10:00
net_inet
pyb
pybnative
stress
thread
unicode
unix py/modsys: Initial implementation of sys.getsizeof(). 2017-08-11 09:43:07 +03:00
wipy
README
pyboard.py
run-bench-tests
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.