micropython/tests
Damien George 2ada1124d4 tests/cpydiff: Remove types_int_tobytesfloat now that it doesn't fail.
Commit e269cabe3e added a check that the
first argument to the to_bytes() method is an integer, and now uPy
follows CPython behaviour and raises a TypeError for this test.

Note: CPython checks the argument types before checking the number of
arguments, but uPy does it the other way around, so they give different
exception messages for this test, but still the same type, a TypeError.
2018-05-08 17:05:32 +10:00
..
basics py/objstr: In find/rfind, don't crash when end < start. 2018-04-05 16:14:17 +10:00
bench
cmdline
cpydiff tests/cpydiff: Remove types_int_tobytesfloat now that it doesn't fail. 2018-05-08 17:05:32 +10:00
extmod
feature_check
float
import
inlineasm
io tests/io/bytesio_ext2: Remove dependency on specific EINVAL value 2018-05-01 15:48:43 +10:00
jni
micropython
misc tests: Move recursive tests to the tests/stress/ subdir. 2018-04-10 14:43:52 +10:00
net_hosted
net_inet
pyb tests/pyb: Update tests to run correctly on PYBv1.0. 2018-05-02 15:25:37 +10:00
pybnative
stress tests: Move recursive tests to the tests/stress/ subdir. 2018-04-10 14:43:52 +10:00
thread
unicode
unix
wipy
README
pyboard.py
run-bench-tests
run-tests tests/run-tests: Support esp32 as a target for running the test suite. 2018-05-02 17:20:48 +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.