orbitzs 3e5a6ea51e add esp8266 project files 4 vuotta sitten
..
basics 3e5a6ea51e add esp8266 project files 4 vuotta sitten
bench 3e5a6ea51e add esp8266 project files 4 vuotta sitten
cmdline 3e5a6ea51e add esp8266 project files 4 vuotta sitten
cpydiff 3e5a6ea51e add esp8266 project files 4 vuotta sitten
extmod 3e5a6ea51e add esp8266 project files 4 vuotta sitten
feature_check 3e5a6ea51e add esp8266 project files 4 vuotta sitten
float 3e5a6ea51e add esp8266 project files 4 vuotta sitten
import 3e5a6ea51e add esp8266 project files 4 vuotta sitten
inlineasm 3e5a6ea51e add esp8266 project files 4 vuotta sitten
io 3e5a6ea51e add esp8266 project files 4 vuotta sitten
jni 3e5a6ea51e add esp8266 project files 4 vuotta sitten
micropython 3e5a6ea51e add esp8266 project files 4 vuotta sitten
misc 3e5a6ea51e add esp8266 project files 4 vuotta sitten
net_hosted 3e5a6ea51e add esp8266 project files 4 vuotta sitten
net_inet 3e5a6ea51e add esp8266 project files 4 vuotta sitten
pyb 3e5a6ea51e add esp8266 project files 4 vuotta sitten
pybnative 3e5a6ea51e add esp8266 project files 4 vuotta sitten
stress 3e5a6ea51e add esp8266 project files 4 vuotta sitten
thread 3e5a6ea51e add esp8266 project files 4 vuotta sitten
unicode 3e5a6ea51e add esp8266 project files 4 vuotta sitten
unix 3e5a6ea51e add esp8266 project files 4 vuotta sitten
wipy 3e5a6ea51e add esp8266 project files 4 vuotta sitten
README 3e5a6ea51e add esp8266 project files 4 vuotta sitten
pyboard.py 3e5a6ea51e add esp8266 project files 4 vuotta sitten
run-bench-tests 3e5a6ea51e add esp8266 project files 4 vuotta sitten
run-tests 3e5a6ea51e add esp8266 project files 4 vuotta sitten
run-tests-exp.py 3e5a6ea51e add esp8266 project files 4 vuotta sitten
run-tests-exp.sh 3e5a6ea51e add esp8266 project files 4 vuotta sitten

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.