micropython/tests
Damien George 4e469085c1 py/objstr: Protect against creating bytes(n) with n negative.
Prior to this patch uPy (on a 32-bit arch) would have severe issues when
calling bytes(-1): such a call would call vstr_init_len(vstr, -1) which
would then +1 on the len and call vstr_init(vstr, 0), which would then
round this up and allocate a small amount of memory for the vstr.  The
bytes constructor would then attempt to zero out all this memory, thinking
it had allocated 2^32-1 bytes.
2018-02-19 16:25:30 +11:00
..
basics py/objstr: Protect against creating bytes(n) with n negative. 2018-02-19 16:25:30 +11:00
bench
cmdline py/repl: Generalise REPL autocomplete to use qstr probing. 2018-02-19 16:12:44 +11:00
cpydiff
extmod extmod/modujson: Implement ujson.dump() function. 2018-02-15 11:35:42 +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 py/repl: Generalise REPL autocomplete to use qstr probing. 2018-02-19 16:12:44 +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.