2779 Commits

Author	SHA1	Message	Date
Angus Gratton	0dac591f97	tests/run-multitests.py: Improve error handling for communication error. ... Fixes fatal crash if serial port access returns an error (for example: port is native USB-CDC and the host hard faults during the test run). Instead of crashing, have the runner mark this as a test run error and continue. It's not certain the next test will run successfully, but this provides the context of output showing what was happening when the communication error occurred. Without this change, that output is lost when the fatal exception terminates the runner process. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-02-26 19:54:47 +11:00
stijn	e08e3d796c	tests/run-tests.py: Output consistent test file paths. ... Test file paths which get passed to the run_tests function can be absolute or relative and with or without leading slash in the latter case, depending on the arguments to run-tests.py, but since that path is used to: - display which tests run - record which tests ran in the results.json - craft the filename for the .exp/.out file for failed tests it is desirable to always use the same file path irregardless of how the user passed the path. In practice this means that all forms of running our own tests like: >python ./run-tests.py -i extmod >python ./run-tests.py -d extmod >python ./run-tests.py -d ./extmod >python ./run-tests.py -d ../tests/extmod >python ./run-tests.py -d /full/path/to/tests/extmod will now consistently all display the tests like pass extmod/time_time_ns.py FAIL extmod/some_failing_test.py and produce output files like results/extmod_some_failing_test.py.exp results/extmod_some_failing_test.py.out instead of displaying/using the exact path as passed. For external tests, meaning not in the tests/ directory, we also want to be consistent so there the choice was made to always use absolute paths. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	7b9163372d	tests/cmdline: Make tests succeed irregardless of invocation path. ... Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	b8098df3a7	tests/run-tests.py: Use normal discovery if tests dir passed explicitly. ... Scan the --test-dirs argument for the main tests directory being passed and if so do the same thing as if running from within that main test directory. In practice this makes the following (which used to counterintuitively try and fail to run the .py files in the tests/ directory itself) >python micropython/tests/run-tests.py -d micropython/tests do the same thing as >cd micropython/tests >python ./run-tests.py which is logical and convenient. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	ff4d4bfade	tests/run-tests.py: Make skip logic work irregardless of test path. ... Test file paths which get passed to the run_tests function can be absolute or relative and with or without leading slash in the latter case, depending on the arguments to run-tests.py, but the skip_tests list with tests to skip only contains relative paths so using simple string equality comparison easily leads to false negatives. Compare the full absolute path instead such that it doesn't matter anymore in which form the tests are passed. Note: - use realpath to resolve symlinks plus make the comparison case insensitive on windows - the test_file passed to run_one_test is not altered by this commit, such that when the user inputs relative paths the tests are also still displayed with relative paths - likewise the test_file_abspath is not modified because functions like run_micropython rely on it having forward slashes In practice this means that it used to be so that the only forms of running tests for which the skip_tests lists actually worked were: >python ./run-tests.py >python ./run-tests.py -d extmod whereas it now works consistently so also for these invocations, which in the end all point to the exact same path: >python ./run-tests.py -d ./extmod >python ./run-tests.py -d ../tests/extmod >python ./run-tests.py -d /full/path/to/tests/extmod These examples used to not skip any of the tests in the extmod/ directory thereby leading to test failures. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
stijn	2ab88c3d58	tests/run-tests.py: Add an argument for showing which tests would run. ... This is convenient when trying to figure out the correct values for --include/--exclude/--test-dirs/... arguments. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
Jeff Epler	2631b0614c	tests/cpydiff: Add a section for throwing incomplete exceptions. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Jeff Epler	20500558f8	tests/micropython: Add a test for throwing incomplete exception. ... This is a reproducer for #17117. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Damien George	6dbabc9267	tests/extmod/os_urandom.py: Add test for os.urandom. ... Signed-off-by: Damien George <damien@micropython.org>	2026-02-24 23:36:51 +11:00
Alessandro Gatti	43a4914fe1	tests/micropython: Add a test for checking viper value clobbering. ... This commit introduces a test that should check whether viper load or store operations won't clobber either the buffer address or the index value being used. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-24 18:42:53 +11:00
Alessandro Gatti	9dcad25de6	py/emitinlinextensa: Add inline assembler support for windowed cores. ... This commit introduces support for writing inline assembler code snippets when targeting Xtensa cores that use register windows (eg. the whole ESP32 family). Opcodes support is still limited to what the ESP8266 supports (as in, LX3 cores opcodes), however each LX core version is guaranteed to support all previous versions' opcodes as well. The ESP32 does not have the inline assembler enabled by default, following the existing expectations when it comes to firmware footprint. Since now emitted functions may have one of two possible exit sequences, the L32I test had to be fixed. It would return the word containing the L32I opcode itself, but the upper 8 bits of the word came from the following opcode - which can change depending on the exit code sequence. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-07 18:36:22 +11:00
Damien George	ee99014e2a	tests/run-tests.py: Broaden the check for raw REPL failure. ... This is a follow up to 6436f8b93f that catches more cases of a failed raw REPL. If the target device is broken in a certain way then it can have a serial write error instead of just not returning any data. In that case the error raised by `pyboard.py` is "could not enter raw repl: Write timeout", which is slightly different to "could not enter raw repl" (the latter is raised when a serial read fails to return the correct data). The patch here accounts for all cases of a failed raw REPL by using `str.startswith()` instead of a string equality. This can be tested on RPI_PICO_W and RPI_PICO2_W which currently crash in the specific way needed to trigger the write timeout when running the `tests/extmod/socket_badconstructor.py` test. In particular adding the following code to the end of a test (eg `tests/extmod/random_extra.py`) will trigger the issue: import socket try: s = socket.socket(socket.AF_INET, socket.SOCK_RAW, None) except TypeError: pass With the fix here, the `run-tests.py` and `run-natmodtests.py` will abort early if that code is added (prior to the fix they would continue to run all tests and take a long time). Signed-off-by: Damien George <damien@micropython.org>	2026-02-06 13:17:43 +11:00
Damien George	570744d06c	py/runtime: Make import-all support non-modules via __dict__/__all__. ... Prior to this fix, `mp_import_all()` assumed that its argument was exactly a native module instance. That would lead to a crash if something else was passed in, eg a user class via a custom `__import__` implementation or by writing to `sys.modules`. MicroPython already supports injecting non-module objects into the import machinery, so it makes sense to round out that implementation by supporting `from x import *` where `x` is a non-module object. Fixes issue #18639. Signed-off-by: Damien George <damien@micropython.org>	2026-02-05 00:24:14 +11:00
Damien George	7ea88f7da2	py/lexer: Add support for nested f-strings within f-strings. ... It turns out that it's relatively simple to support nested f-strings, which is what this commit implements. The way the MicroPython f-string parser works at the moment is: 1. it extracts the f-string arguments (things in curly braces) into a temporary buffer (a vstr) 2. once the f-string ends (reaches its closing quote) the lexer switches to tokenizing the temporary buffer 3. once the buffer is empty it switches back to the stream. The temporary buffer can easily hold f-strings itself (ie nested f-strings) and they can be re-parsed by the lexer using the same algorithm. The only thing stopping that from working is that the temporary buffer can't be reused for the nested f-string because it's currently being parsed. This commit fixes that by adding a second temporary buffer, which is the "injection" buffer. That allows arbitrary number of nestings with a simple modification to the original algorithm: 1. when an f-string is encountered the string is parsed and its arguments are extracted into `fstring_args` 2. when the f-string finishes, `fstring_args` is inserted into the current position in `inject_chrs` (which is the start of that buffer if no injection is ongoing) 3. `fstring_args` is now cleared and ready for any further f-strings (nested or not) 4. the lexer switches to `inject_chrs` if it's not already reading from it 5. if an f-string appeared inside the f-string then it is in `inject_chrs` and can be processed as before, extracting its arguments into `fstring_args`, which can then be inserted again into `inject_chrs` 6. once `inject_chrs` is exhausted (meaning that all levels of f-strings have been fully processed) the lexer switched back to tokenizing the stream. Amazingly, this scheme supports arbitrary numbers of nestings of f-strings using the same quote style. This adds some code size and a bit more memory usage for the lexer. In particular for a single (non-nested) f-string it now makes an extra copy of the `fstring_args` data, when copying it across to `inject_chrs`. Otherwise, memory use only goes up with the complexity of nested f-strings. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 23:19:09 +11:00
Damien George	617c7dba3b	py/lexer: Use null char as lexer EOF sentinel. ... The null byte cannot exist in source code (per CPython), so use it to indicate the end of the input stream (instead of `(mp_uint_t)-1`). This allows the cache chars (chr0/1/2 and their saved versions) to be 8-bit bytes, making it clear that they are not `unichar` values. It also saves a bit of memory in the `mp_lexer_t` data structure. (And in a future commit allows the saved cache chars to be eliminated entirely by storing them in a vstr instead.) In order to keep code size down, the frequently used `chr0` is still of type `uint32_t`. Having it 32-bit means that machine instructions to load it are smaller (it adds about +80 bytes to Thumb code if `chr0` is changed to `uint8_t`). Also add tests for invalid bytes in the input stream to make sure there are no regressions in this regard. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 23:19:09 +11:00
Damien George	6436f8b93f	tests/run-tests.py: Abort test run if enter_raw_repl fails many times. ... Prior to this change, if a test crashed a board to the point that it was no longer responsive but the serial connection was still alive and able to read/write (eg due to an infinite loop with ctrl-C unavailable), it would take (30 + 10 * number-of-remaining-tests) seconds to finish the test run. That can be 10 minutes or more. The change here aborts the test run if the target does not respond 4 times to when trying to enter the raw REPL at the start of a test. Now, it only takes a maximum of (30 + 4 * 5) = 50 seconds to detect a crashed state and abort the entire test run. Can test this by adding the following to a test: import time, micropython micropython.kbd_intr(-1) while 1: time.sleep(1) For example, add the above to the end of `tests/extmod/random_extra.py` and test via: $ ./run-tests.py -t a0 extmod/[r-z]*.py $ ./run-natmodtests.py -t a0 extmod/[r-z]*.py Previously the `run-tests.py` run would take around 16 minutes. Now it takes under a minute. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 20:17:11 +11:00
Damien George	f624200b31	tests/test_utils.py: Abort test if serial port fails at start. ... All test runners (except `run-multitests.py`) will now abort with error code 2 if the target is a serial port and could not be detected, ie `enter_raw_repl` failed at the detection stage. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 20:17:11 +11:00
Damien George	a1d4f6256c	tests/run-tests.py: Exit with error code 2 if test runner fails. ... The tests runners usually exit with error code 1 when something fails. But it's useful to distinguish between "a test failed" and "the test runner failed". To that end, `run-tests.py` now returns error code 2 when unittest is not installed but is needed. And `run-natmodtests.py` now returns error code 2 when it cannot automatically detect the target architecture. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 20:17:11 +11:00
Damien George	cef2538b10	tests/target_wiring/README: Add README describing target_wiring specs. ... This is now the authoritative place for what should go in a target wiring script. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:59:38 +11:00
Damien George	d291a280bd	tests/target_wiring: Add SPI instance for mimxrt, nrf, renesas-ra, samd. ... Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:59:19 +11:00
Damien George	e5f772ae85	tests/extmod/machine_spi_rate.py: Use target wiring for SPI instances. ... This commit converts `tests/extmod/machine_spi_rate.py` to use the target wiring mechanism, moving the port-specefic definition of the SPI instances that are being tested out of the `tests/extmod/machine_spi_rate.py` file and into the target wiring code. As part of this, the test is changed to always use the default pins for the given SPI instance. This simplifies the test, makes it easier to add support for new ports/boards, and allows reusing the `spi_standalone_args_list` definition in other tests (if needed one day). Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:59:19 +11:00
Damien George	edab53c1da	tests/multi_net: Use random.getrandbits instead of random.randrange. ... The `getrandbits()` function is guaranteed to exist on all ports that have the `random` module (but `randrange()` is not). Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:35:00 +11:00
Damien George	e40d609a0e	tests/multi_net: Skip all ssl/tls tests on axTLS. ... The axTLS implementation of the tls module only has a basic set of features. In particular it doesn't support the CERT_REQUIRED constant nor DTLS, nor can it load the `ec_key.der` key when acting as a server. So skip tests that require these features, which ends up being all the ssl/tls tests. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:35:00 +11:00
Damien George	96bce47762	tests: Factor out common helper functions to separate Python module. ... The test runners have evolved over time and become more and more complex. In particular `tests/run-tests.py` is rather large now. The test runners also duplicate some functionality amongst themselves. As a start to improving this situation, this commit factors out the helper functions from `run-tests.py` into a new `test_utils.py` file, and uses that new module in all test runners. There should be no functional change here. Signed-off-by: Damien George <damien@micropython.org>	2026-01-30 17:03:08 +11:00
Damien George	93692caefa	extmod/modmarshal: Support marshal.dumps of functions with children. ... This commit adds support to the `marshal` module to be able to dump functions that have child functions. For example: import marshal def f(): def child(): return 1 return child marshal.dumps(f.__code__) It also covers the case of marshalling functions that use list comprehensions, because a list comprehension uses a child function. This is made possible by the newly enhanced `mp_raw_code_save_fun_to_bytes()` that can now handle nested functions. Unmarshalling via `marshal.loads()` already supports nested functions because it uses the standard `mp_raw_code_load_mem()` function which is used to import mpy files (and hence can handle all possibilities). Signed-off-by: Damien George <damien@micropython.org>	2026-01-27 01:20:36 +11:00
Damien George	878f8004fd	py/objfun: Support __code__ on functions with children. ... If a function has children then the code object returned from __code__ must contain an `mp_raw_code_t` (actually `mp_raw_code_truncated_t` is enough) that points to the child table. Signed-off-by: Damien George <damien@micropython.org>	2026-01-27 01:20:36 +11:00
Damien George	25b400f688	tests/multi_net/tcp_client_rst.py: Improve and extend test. ... These changes test a few more things related to TCP RST: - add a second iteration to drain incoming data after TCP RST - read data after closing socket Signed-off-by: Damien George <damien@micropython.org>	2026-01-27 00:49:34 +11:00
Jeff Epler	f918e33645	tests/thread/stress_schedule.py: Remove decorator/inaccurate comment. ... This test can now run correctly with the native emitter because the `thread()` function will run the scheduler during the call to `time.sleep_ms(1)`. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-26 23:33:49 +11:00
Jeff Epler	78ec31b175	tests/run-tests.py: Re-enable some asyncio tests for the native emitter. ... These tests no longer fail under the native emitter. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-26 23:33:49 +11:00
Jeff Epler	f3874842ab	tests/micropython: Add new schedule_sleep.py test. ... This variant of `schedule.py` explicitly calls a zero sleep. The existing variant is kept to ensure the scheduler is called between bytecodes. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-26 23:33:49 +11:00
Jeff Epler	cfaba3211c	tests/thread/stress_schedule.py: Decrease backoff time. ... Locally, this changes the duration of the test from about 2.7s to 0.3s. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-26 23:03:40 +11:00
Jeff Epler	b792efc341	tests/run-tests.py: Re-add stress_schedule.py for GitHub Actions. ... This test was ignored since 2020, which hid a new bug in the test for the native emitter added in 2024. Hopefully other changes to the test will make it more reliable. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-26 23:02:48 +11:00
Alessandro Gatti	b14d129a16	tests/float/complex1.py: Fix CPython 3.14 deprecation. ... This commit fixes a test exercising complex numbers creation, working around a deprecation introduced in CPython 3.14. Creating complex numbers using a complex number as the real part in the constructor is deprecated in CPython 3.14, but that construction method is still supported by MicroPython and covered by tests. To work around this, the specific constructor is extracted into its own test, providing an expected output file recorded using CPython 3.11. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-15 21:10:30 +01:00
Alessandro Gatti	eae83df201	tests/float/math_fun: Fix domain error tests with CPython 3.14. ... This commit makes tests exercising certain math functions' limit work when using CPython 3.14 to validate the tests' output. CPython 3.14 introduced more descriptive messages when math domain error conditions are encountered rather than a single generic message. This breaks the tests in question as MicroPython uses a single error message when reporting these conditions (both to closely follow CPython and to save firmware space). The math domain tests now look for an error pattern that is compatible with both CPython 3.14 and previous versions, converting messages in the newer format into the previous one. This makes the tests' behaviour under MicroPython comparable with CPython for the foreseeable future. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-15 20:53:33 +01:00
Alessandro Gatti	e66a1a3f4a	tests/basics/try_finally: Fix try/finally flow tests under CPython 3.14. ... This commit fixes tests that will always fail when using CPython 3.14 to get a known-good output to compare MicroPython's behaviour against. Starting from CPython 3.14, statements inside a `finally` block that will prevent the execution flow to reach the block's last statement will raise a SyntaxWarning. That text would end up in the comparison data and thus make known-good tests fail. Given that those tests explicitly exercise flow control interruptions in finally blocks, there is no real workaround that can be applied to the tests themselves. Therefore those tests will now check MicroPython's behaviour against expected output files recorded from the tests' output with CPython 3.11. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-15 20:53:26 +01:00
Alessandro Gatti	e939d3ec76	tools/mpy_ld.py: Add RV64 natmod support. ... This commit adds the ability to compile native modules for the RV64 platform, using "rv64imc" as its architecture name (eg. "make ARCH=rv64imc" should build a RV64 natmod). The rest of 64-bits relocations needed to build a native module are now implemented, and all sample native modules build without errors or warnings. The same Picolibc caveats on RV32 also apply on RV64, thus the documentation was updated accordingly. RV64 native modules are also built as part of the CI process, but not yet executed as the QEMU port is not yet able to load and run them. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-30 18:18:42 +01:00
Alessandro Gatti	7173ddee5f	tests/run-natmodtests.py: Explicitly open prelude file. ... This change lets the natmod test runner report status information on session end if a prelude script file is chosen. The script serialises its input data as part of the end of session reporting data, but since the prelude file is not a serialisable object serialisation would fail (it's a file handle as far as the argument container structure is aware). Now the file is explicitly open by the script rather than relying on argparse's file handle argument class wrapper. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:51:56 +01:00
Alessandro Gatti	1df86516e0	py/asmrv32: Reserve a flag for the Zcmp RV32 CPU extension. ... This commit performs the necessary changes to handle an additional RV32 CPU extension flag, for the Zcmp extension in this case. The changes are not limited to RV32-only code, as other parts of the tooling need to be modified for this: the testing framework has to be made aware that an extra bit can be set in sys.implementation._mpy and needs to know how it is called, and "mpy-cross" must be able to actually set that flag bit in the first place via the appropriate command line argument. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
Alessandro Gatti	cb9d8fcc31	tests/run-tests.py: Discover RV32 extension inlineasm tests. ... This commit extends the test runner to automatically discover inline assembler tests for known RV32 extensions, and checks whether to add the discovered tests to the enabled tests list. Automatic discovery requires that inline assembler tests for RV32 extensions follow a specific pattern both for filenames and for the tests' output in case of success. A valid RV32 extension test must have: * A code fragment that checks for support of the extension on the running target in "/tests/feature_check", called "inlineasm_rv32_<extensionname>.py" that should print the string "rv32_<extensionname>" if the extension is supported * A matching expected result file in "/tests/feature_check" called "inlineasm_rv32_<extensionname>.py.exp" that must contain the string "rv32_<extensionname>" (without quotes) * A regular MicroPython test file in "/tests/inlineasm/rv32" called "asm_ext_<extensionname>.py" For example, to test the Zba extension, there must be a file called "/tests/feature_check/inlineasm_rv32_zba.py" that should print the string "rv32_zba" if the extension is supported, together with a file called "/test/feature_check/inlineasm_rv32_zba.py.exp" that contains the string "rv32_zba" in it, and finally there must be a regular MicroPython test file called "/tests/inlineasm/rv32/asm_ext_zba.py". Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
Alessandro Gatti	9c9b99686e	tests/target_wiring: Provide an ESP8266 target wiring module. ... This commit introduces ESP8266 support for target wiring tests, fixing execution of relevant tests that once failed on that platform. ESP8266 boards need to have GPIO4 and GPIO5 connected together to provide a UART loopback, in order to test whether UART data effectively flows through. The wiring-enabled UART transmission timing test was also updated with measurements compatible with a few ESP8266 test boards. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-17 16:05:49 +11:00
Alessandro Gatti	dbf59db5a1	tests/extmod/vfs_blockdev_invalid.py: Handle low memory conditions. ... This commit modifies the "extmod/vfs_blockdev_invalid" test to better behave on boards with low available memory. Before these changes the test would fail on ESP8266 (at least), due to low memory, but in a way that could not be easily solved as the error occurred in the middle of the test. The test has been rewritten to delay its output until the very end, so if a low memory condition occurs and needs to stop execution then no real output will show up before the skip marker. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-17 16:05:29 +11:00
Alessandro Gatti	750a366f20	tests/run-tests.py: Skip list sort stress test for ESP8266. ... This commit marks the "stress/list_sort.py" test to be skipped when running on ESP8266. The test just takes too long without yielding to the OS whilst doing the sort, causing the internal software watchdog to kick in and reboot the board. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-17 16:05:18 +11:00
Jeff Epler	ef567dc928	tests/basics/string_fstring.py: Test fstring nested replacement fields. ... This does not actually cover any additional lines, but it does cover new functionality not previously covered. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-12-17 00:14:59 +11:00
Damien George	b78fac161e	tests/ports/esp32/check_err_str.py: Preallocate global variable. ... This test fails on all esp32 boards without this fix, because the try/except that runs with the heap locked attempts to increase the size of the globals dict when assigning to the exception variable `e`. Fix that by preallocating the global variable `e`. Signed-off-by: Damien George <damien@micropython.org>	2025-12-16 23:37:59 +11:00
Anson Mansfield	c25667f6a9	tests/basics/builtin_help.py: Test correct handling of deleted entries. ... This test reproduces the bug that gave rise to the esp32 segfaults in issues #18061 and #18481 on all platforms. Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-12-07 18:22:56 +11:00
Damien George	d357eff2bc	tests/net_inet: Update micropython.org certificate for SSL tests. ... Signed-off-by: Damien George <damien@micropython.org>	2025-12-07 15:49:52 +11:00
Damien George	9939eae599	tests/serial_test.py: Add a serial echo test. ... The existing `serial_test.py` script tests data in/out throughput and reliability. But it only tests data sizes that are a power of two, which may not catch certain errors with USB transmission (because FS packet size is 64 bytes). This commit adds a new echo sub-test to the `serial_test.py` script. It sends out data to the target and gets the target to echo it back, and then compares the result (the echo'd data should be equal to the sent data). It does this for data packets between 1 and 520 (inclusive) bytes, which covers USB FS and HS packet sizes (64 and 512 respectively). It uses random data for the test, but seeded by a constant seed so that it's deterministic. If there's an error then it prints out all the sent and echo'd data to make it easier to see where it went wrong (eg if the previous packet was repeated). Signed-off-by: Damien George <damien@micropython.org>	2025-12-07 15:29:28 +11:00
Damien George	37bac07f5d	tests/serial_test.py: Factor common reset code into send_script func. ... Signed-off-by: Damien George <damien@micropython.org>	2025-12-07 15:29:06 +11:00
Angus Gratton	938e2c0f2b	tests/multi_espnow: Add test case for espnow rate changes. ... Uses constants added in previous commit. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-25 11:56:33 +11:00
Andrew Leech	e067d96c8b	tests/run-tests.py: Add general newline normalization function. ... Add a general normalize_newlines() function that handles newline variations (\\r\\r\\n, \\r\\n) to \\n while preserving literal \\r characters that are part of test content. This provides a robust solution for cross-platform test compatibility, particularly addressing PTY double-newline issues that can occur with some terminal implementations. The function is applied to all test output before comparison, eliminating platform-specific newline issues. Includes a unit test to verify the normalization behavior. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-11-22 00:06:59 +11:00