micropython/tests
Paul Sokolovsky 2ec38a17d4 objstr: Be 8-bit clean even for repr().
This will allow roughly the same behavior as Python3 for non-ASCII strings,
for example, print("<phrase in non-Latin script>".split()) will print list
of words, not weird hex dump (like Python2 behaves). (Of course, that it
will print list of words, if there're "words" in that phrase at all, separated
by ASCII-compatible whitespace; that surely won't apply to every human
language in existence).
2014-06-14 01:21:13 +03:00
..
basics objstr: Be 8-bit clean even for repr(). 2014-06-14 01:21:13 +03:00
bench tests/bench: Add testcase for positional/kwargs to enumerate(). 2014-05-07 22:34:06 +03:00
bytecode fix README to match contents of run-tests 2014-04-16 20:14:38 +01:00
float py: Raise TypeError when trying to format non-int with %x,%o,%X. 2014-06-05 19:44:54 +01:00
import tests: Move gen_context to import tests, because it relies on import. 2014-04-17 23:21:52 +01:00
inlineasm tests: Add inline assembler test for pyboard. 2014-05-07 18:31:14 +01:00
io py: Rename builtin "io" to "_io". 2014-06-12 01:22:25 +03:00
micropython tests: Add feature test for when heap allocation is disabled. 2014-05-31 18:33:16 +01:00
misc tests: Make rge-sm.py use less memory (integration step increased). 2014-04-04 11:15:54 +00:00
pyb stmhal: Fix setting of RTC: was BCD now BIN encoded. 2014-05-10 11:56:58 +01:00
pybnative py: Fix stack access in thumb native emitter. 2014-05-07 23:27:45 +01: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 tests: Run 'micropython' tests on pyboard. 2014-06-08 13:46:03 +01: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.