micropython

History

Paul Sokolovsky 2cf381081a run-tests: Add option to write CPython's test results to .exp files.

Mostly to run testsuite on targets which doesn't have CPython.

2014-07-12 16:34:51 +03:00

basics

tests: Rename test scripts, changing - to _ for consistency.

2014-07-05 06:14:29 +01: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

moductypes: Add symbolic constants to specify bitfield position/length.

2014-07-11 00:06:36 +03:00

float

tests: Rename test scripts, changing - to _ for consistency.

2014-07-05 06:14:29 +01:00

import

tests: Rename test scripts, changing - to _ for consistency.

2014-07-05 06:14:29 +01:00

inlineasm

tests: Add inline assembler test for pyboard.

2014-05-07 18:31:14 +01:00

tests: Rename test scripts, changing - to _ for consistency.

2014-07-05 06:14:29 +01:00

micropython

tests: Add feature test for when heap allocation is disabled.

2014-05-31 18:33:16 +01:00

misc

tests: Rename test scripts, changing - to _ for consistency.

2014-07-05 06:14:29 +01: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

unicode

tests: Add basic test for unicode file i/o.

2014-06-27 00:04:20 +03: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

run-tests: Add option to write CPython's test results to .exp files.

2014-07-12 16:34:51 +03: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.