Startseite Erkunden Hilfe
Registrieren Anmelden
gogadmin
/
Arduino
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki
Branch: master
Branches Tags
Arduino
/
esp8266
/
micropython
/
tests
orbitzs 3e5a6ea51e add esp8266 project files vor 4 Jahren
..
basics 3e5a6ea51e add esp8266 project files vor 4 Jahren
bench 3e5a6ea51e add esp8266 project files vor 4 Jahren
cmdline 3e5a6ea51e add esp8266 project files vor 4 Jahren
cpydiff 3e5a6ea51e add esp8266 project files vor 4 Jahren
extmod 3e5a6ea51e add esp8266 project files vor 4 Jahren
feature_check 3e5a6ea51e add esp8266 project files vor 4 Jahren
float 3e5a6ea51e add esp8266 project files vor 4 Jahren
import 3e5a6ea51e add esp8266 project files vor 4 Jahren
inlineasm 3e5a6ea51e add esp8266 project files vor 4 Jahren
io 3e5a6ea51e add esp8266 project files vor 4 Jahren
jni 3e5a6ea51e add esp8266 project files vor 4 Jahren
micropython 3e5a6ea51e add esp8266 project files vor 4 Jahren
misc 3e5a6ea51e add esp8266 project files vor 4 Jahren
net_hosted 3e5a6ea51e add esp8266 project files vor 4 Jahren
net_inet 3e5a6ea51e add esp8266 project files vor 4 Jahren
pyb 3e5a6ea51e add esp8266 project files vor 4 Jahren
pybnative 3e5a6ea51e add esp8266 project files vor 4 Jahren
stress 3e5a6ea51e add esp8266 project files vor 4 Jahren
thread 3e5a6ea51e add esp8266 project files vor 4 Jahren
unicode 3e5a6ea51e add esp8266 project files vor 4 Jahren
unix 3e5a6ea51e add esp8266 project files vor 4 Jahren
wipy 3e5a6ea51e add esp8266 project files vor 4 Jahren
README 3e5a6ea51e add esp8266 project files vor 4 Jahren
pyboard.py 3e5a6ea51e add esp8266 project files vor 4 Jahren
run-bench-tests 3e5a6ea51e add esp8266 project files vor 4 Jahren
run-tests 3e5a6ea51e add esp8266 project files vor 4 Jahren
run-tests-exp.py 3e5a6ea51e add esp8266 project files vor 4 Jahren
run-tests-exp.sh 3e5a6ea51e add esp8266 project files vor 4 Jahren

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.