micropython

History

Paul Sokolovsky 1ca28bd570 run-tests: Reset MICROPYPATH, to make sure tests use only builtin modules.		2014-12-12 00:58:07 +02:00
..
basics	tests: Add test for semantics of for-loop that optimisation can break.	2014-12-11 17:40:41 +00:00
bench	bench: Three ways to process a byte buffer.	2014-06-19 22:27:13 +03:00
bytecode	fix README to match contents of run-tests	2014-04-16 20:14:38 +01:00
extmod	tests: Add test for hashlib.sha256 .	2014-11-22 14:54:02 +02:00
float	tests: Split out float test from builtin_round.py.	2014-11-29 14:47:54 +00:00
import	py: Implement __file__ attribute for modules.	2014-07-28 21:21:59 +03:00
inlineasm	tests: Add inline assembler test for pyboard.	2014-05-07 18:31:14 +01:00
io	py: Make stream seek correctly check for ioctl fn; add seek for textio.	2014-11-16 23:56:37 +00:00
micropython	tests: Add heapalloc.py.exp, since CPython can't generate it.	2014-10-31 22:09:40 +00:00
misc	tests: Activate recursive_data.py test, now that io.StringIO is available.	2014-12-12 00:58:07 +02:00
pyb	Adding CAN filter management	2014-11-26 18:52:33 +00:00
pybnative	py: Fix stack access in thumb native emitter.	2014-05-07 23:27:45 +01:00
unicode	Use mode/encoding kwargs in io and unicode tests	2014-10-21 22:10:38 +03:00
unix	tests: Skip ffi_float.py if module ffi is not available.	2014-10-06 22:37:40 +03:00
README	tests: Split out those tests requiring float and import.	2014-04-17 16:21:43 +01:00
pyboard.py	tests: Add a suite of tests specifically for the pyboard.	2014-05-03 16:43:27 +01:00
run-bench-tests	tests: Add framework for comparative benchmarking.	2014-05-05 01:24:16 +03:00
run-tests	run-tests: Reset MICROPYPATH, to make sure tests use only builtin modules.	2014-12-12 00:58:07 +02:00
run-tests-exp.sh	tests: Force skip of LE test on non-LE arch; improve run-tests-exp.sh.	2014-10-06 17:35:46 +00:00

README

This directory contains tests for various functionality areas of MicroPython.
To run all stable tests, run "run-tests" script in this directory. Note
that bytecode tests are not yet stable and should be run separately in
"bytecode" subdirectory.

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.