micropython/tests
Damien George d77da83d55 py/objrange: Implement (in)equality comparison between range objects.
This feature is not often used so is guarded by the config option
MICROPY_PY_BUILTINS_RANGE_BINOP which is disabled by default.  With this
option disabled MicroPython will always return false when comparing two
range objects for equality (unless they are exactly the same object
instance).  This does not match CPython so if (in)equality between range
objects is needed then this option should be enabled.

Enabling this option costs between 100 and 200 bytes of code space
depending on the machine architecture.
2018-02-14 23:17:06 +11:00
..
basics py/objrange: Implement (in)equality comparison between range objects. 2018-02-14 23:17:06 +11:00
bench
cmdline tests: Add some more tests to improve coverage of py/parse.c. 2017-12-19 16:13:00 +11:00
cpydiff
extmod extmod/vfs_fat_file: Implement SEEK_CUR for non-zero offset. 2018-01-31 17:33:07 +11:00
feature_check
float py/objfloat: Fix case of raising 0 to -infinity. 2018-02-08 14:35:43 +11:00
import
inlineasm
io
jni
micropython tests: Automatically skip tests that require eval, exec or frozenset. 2018-02-14 16:46:44 +11:00
misc
net_hosted
net_inet
pyb
pybnative
stress
thread
unicode
unix tests/unix: Add coverage test for calling mp_obj_new_bytearray. 2018-02-08 11:14:30 +11:00
wipy
README
pyboard.py
run-bench-tests
run-tests tests/run-tests: Capture any output from a crashed uPy execution. 2018-02-14 17:24:59 +11: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.