micropython/tests
2015-03-12 00:17:04 +00:00
..
basics py: Add support for start/stop/step attributes of builtin range object. 2015-03-11 20:02:06 +00:00
bench py: Use sequence of strings for named tuple initialization 2015-01-01 14:53:23 +02:00
bytecode fix README to match contents of run-tests 2014-04-16 20:14:38 +01:00
extmod tests: Add zlib test for decompressing uncompressed data. 2015-03-12 00:17:04 +00:00
float tests: Add tests for boundmeth; and bignum cmp, unary, float, error. 2015-03-03 16:45:39 +00:00
import tests: Add another testcase for relative imports. 2015-02-16 12:11:41 +02:00
inlineasm tests: Add tests for inline assembler beq_n and beq_w ops. 2015-03-02 14:31:00 +00:00
io tests: Add some tests to improve coverage. 2015-01-29 14:56:09 +00:00
micropython tests: Add test for micropython const feature when it has a SyntaxError. 2015-03-01 12:06:24 +00:00
misc py: Fix adding of traceback so that it appends to existing info. 2015-02-27 00:36:39 +00:00
pyb tests: Update pyb/uart.py test since baudrate of 1200 is too low. 2015-02-27 00:40:08 +00:00
pybnative py: Fix stack access in thumb native emitter. 2014-05-07 23:27:45 +01:00
unicode tests: Add some tests to improve coverage. 2015-01-29 14:56:09 +00:00
unix tests: Make ffi_callback.py be able to run on uclibc and macosx. 2015-01-10 00:35:48 +02:00
pyboard.py tests: Add a suite of tests specifically for the pyboard. 2014-05-03 16:43:27 +01:00
README tests: Split out those tests requiring float and import. 2014-04-17 16:21:43 +01:00
run-bench-tests tests: Add framework for comparative benchmarking. 2014-05-05 01:24:16 +03:00
run-tests tests: Skip basics/boundmeth1.py for native emitter. 2015-03-03 18:06:45 +00:00
run-tests-exp.py tests: Add run-tests-exp.py, simple MicroPython-based test runner. 2014-12-24 16:34:05 +00:00
run-tests-exp.sh run-tests-exp.sh: Typo fix in comment. 2015-02-21 03:22:33 +02:00

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.