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

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.