mirrors/micropython
1
0
Fork 0
mirror of https://github.com/licsber/micropython.git synced 2024-09-20 17:10:24 +08:00
Code Issues Packages Projects Releases Wiki Activity
7a6e09635a
micropython/tests
History
Chris Angelico 7a6e09635a Remove tests that fail under CPython 3.5 
See http://bugs.python.org/issue19995 for rationale. As micropython currently
aims for Python 3.3 compatibility I have not changed behaviour, but this
change allows the test suite to be run against a newer Python without having
spurious failures.
2014-06-05 22:34:11 +10:00
..
basics py: Implement full behaviour of dict.update(), and dict(). 2014-06-03 12:53:44 +01: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 Remove tests that fail under CPython 3.5 2014-06-05 22:34:11 +10: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, stream: Implement readlines for a stream. 2014-05-03 22:01:32 +01: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
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: Change --test_dirs to --test-dirs. 2014-05-31 18:11:01 +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.