6 Commity (59a7865a7d667b3c660b53b0cf223bd1f82bad46)

Autor	SHA1	Wiadomość	Data
Jim Mussared	59a7865a7d	tests/run-multitests.py: Add shortcuts for local Python instances. ... One can now use `-i micropython` and `-i cpython` to add instances using the `MICROPYTHON` and `CPYTHON3` variables (which can be overridden by env vars).	2020-04-29 16:45:46 +10:00
Jim Mussared	f588138bbe	tests/run-multitests.py: Allow filtering out lines from stdout. ... And use this new feature to filter out certain lines in the Bluetooth multitests.	2020-04-29 16:45:46 +10:00
David Lechner	3dc324d3f1	tests: Format all Python code with black, except tests in basics subdir. ... This adds the Python files in the tests/ directory to be formatted with ./tools/codeformat.py. The basics/ subdirectory is excluded for now so we aren't changing too much at once. In a few places `# fmt: off`/`# fmt: on` was used where the code had special formatting for readability or where the test was actually testing the specific formatting.	2020-03-30 13:21:58 +11:00
Damien George	18fa65e474	tests: Make default MICROPYPATH include extmod to find uasyncio.	2020-03-26 01:25:45 +11:00
Damien George	19ea30bdd5	tests/run-multitests.py: Print test summary and do exit(1) on failure.	2020-03-18 21:33:40 +11:00
Damien George	df9a949891	tests/run-multitests.py: Add new test runner for multiple Py instances. ... This commit adds a test runner and initial test scripts which run multiple Python/MicroPython instances (eg executables, target boards) in parallel. This is useful for testing, eg, network and Bluetooth functionality. Each test file has a set of functions called instanceX(), where X ranges from 0 up to the maximum number of instances that are needed, N-1. Then run-multitests.py will execute this script on N separate instances (eg micropython executables, or attached boards via pyboard.py) at the same time, synchronising their start in the right order, possibly passing IP address (or other address like bluetooth MAC) from the "server" instance to the "client" instances so they can connect to each other. It then runs them to completion, collects the output, and then tests against what CPython gives (or what's in a provided .py.exp file). The tests will be run using the standard unix executable for all instances by default, eg: $ ./run-multitests.py multi_net/*.py Or they can be run with a board and unix executable via: $ ./run-multitests.py --instance pyb:/dev/ttyACM0 --instance exec:micropython multi_net/*.py	2020-03-10 02:22:34 +11:00