You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Damien George f256cfef4f tests: Add some more tests for complex numbers and ure module. 10 years ago
..
basics py: Fix builtin abs so it works for bools and bignum. 10 years ago
bench py: Use sequence of strings for named tuple initialization 10 years ago
bytecode fix README to match contents of run-tests 11 years ago
cmdline tests: Don't try to verify amount of memory used in cmd_showbc test. 10 years ago
extmod tests: Add some more tests for complex numbers and ure module. 10 years ago
float tests: Add some more tests for complex numbers and ure module. 10 years ago
import tests: Add another testcase for relative imports. 10 years ago
inlineasm tests: Add tests for inline assembler beq_n and beq_w ops. 10 years ago
io tests: Add some tests to improve coverage. 10 years ago
micropython tests: Add tests for things that are not already tested. 10 years ago
misc py: Fix adding of traceback so that it appends to existing info. 10 years ago
pyb stmhal: Fix adc.read_timed so buffer store respects element size. 10 years ago
pybnative py: Fix stack access in thumb native emitter. 11 years ago
unicode tests: Add some tests to improve coverage. 10 years ago
unix tests: Make ffi_callback.py be able to run on uclibc and macosx. 10 years ago
README tests: Split out those tests requiring float and import. 11 years ago
pyboard.py tests: Add a suite of tests specifically for the pyboard. 11 years ago
run-bench-tests tests: Add framework for comparative benchmarking. 11 years ago
run-tests tests: Add ability to test uPy cmdline executable. 10 years ago
run-tests-exp.py tests: Add run-tests-exp.py, simple MicroPython-based test runner. 10 years ago
run-tests-exp.sh run-tests-exp.sh: Typo fix in comment. 10 years ago

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.