You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Damien George c5a21a94f8 extmod/modbluetooth: Provide FLAG_WRITE_NO_RESPONSE for characteristics. 5 years ago
..
basics tests/basics/dict_pop.py: Remove extra comma in call and fix grammar. 5 years ago
cmdline tests: Format all Python code with black, except tests in basics subdir. 5 years ago
cpydiff tests: Format all Python code with black, except tests in basics subdir. 5 years ago
extmod docs,tests: Add docs and test for uasyncio custom exc handler methods. 5 years ago
feature_check tests: Format all Python code with black, except tests in basics subdir. 5 years ago
float tests/float: Add new lexer test to test parsing of float without prefix. 5 years ago
import tests: Format all Python code with black, except tests in basics subdir. 5 years ago
inlineasm tests: Format all Python code with black, except tests in basics subdir. 5 years ago
internal_bench tests: Format all Python code with black, except tests in basics subdir. 5 years ago
io tests: Format all Python code with black, except tests in basics subdir. 5 years ago
jni tests: Format all Python code with black, except tests in basics subdir. 5 years ago
micropython py/objexcept: Allow compression of exception message text. 5 years ago
misc tests: Format all Python code with black, except tests in basics subdir. 5 years ago
multi_bluetooth extmod/modbluetooth: Provide FLAG_WRITE_NO_RESPONSE for characteristics. 5 years ago
multi_net tests/multi_net: Add uasyncio test for TCP server and client. 5 years ago
net_hosted tests: Format all Python code with black, except tests in basics subdir. 5 years ago
net_inet tests: Format all Python code with black, except tests in basics subdir. 5 years ago
perf_bench tests: Format all Python code with black, except tests in basics subdir. 5 years ago
pyb tests: Format all Python code with black, except tests in basics subdir. 5 years ago
pybnative tests: Format all Python code with black, except tests in basics subdir. 5 years ago
qemu-arm qemu-arm: Add testing of frozen native modules. 5 years ago
stress tests: Format all Python code with black, except tests in basics subdir. 5 years ago
thread tests: Format all Python code with black, except tests in basics subdir. 5 years ago
unicode tests: Format all Python code with black, except tests in basics subdir. 5 years ago
unix tests: Format all Python code with black, except tests in basics subdir. 5 years ago
wipy tests: Format all Python code with black, except tests in basics subdir. 5 years ago
README tests: Make run-tests help and README be more descriptive of behaviour. 5 years ago
run-internalbench.py tests: Format all Python code with black, except tests in basics subdir. 5 years ago
run-multitests.py tests: Format all Python code with black, except tests in basics subdir. 5 years ago
run-natmodtests.py tests: Format all Python code with black, except tests in basics subdir. 5 years ago
run-perfbench.py tests: Format all Python code with black, except tests in basics subdir. 5 years ago
run-tests tests/run-tests: Add commands to print and clean *.exp,out files. 5 years ago
run-tests-exp.py tests: Format all Python code with black, except tests in basics subdir. 5 years ago
run-tests-exp.sh run-tests-exp.sh: Typo fix in comment. 10 years ago

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.

Tests are generally verified by running the test both in MicroPython and
in CPython and comparing the outputs. If the output differs the test fails
and the outputs are saved in a .out and a .exp file respectively.
For tests that cannot be run in CPython, for example because they use
the machine module, a .exp file can be provided next to the test's .py
file. A convenient way to generate that is to run the test, let it fail
(because CPython cannot run it) and then copy the .out file (but not
before checking it manually!)

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.