ElixirForge/DFTE
1
0
Fork 0
mirror of https://github.com/alexhopeoconnor/DFTE.git synced 2026-10-22 14:47:48 +10:00
Code Releases Activity

ci: add current ESP32 validation lane

Browse Source
This commit is contained in:
alex
2026-09-17 12:10:53 +10:00
parent 42cb8f2324
commit ec4c32db32
11 changed files with 113 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/TESTING.md
+16 -2
View File
@@ -1,15 +1,29 @@
# Testing
The two PlatformIO Unity commands compile the complete DFTE test suites without uploading or executing them, so they require no attached board.
The three PlatformIO Unity commands compile the complete DFTE test suites without uploading or executing them, so they require no attached board.
```bash
./scripts/test.sh compile --platform esp8266
./scripts/test.sh compile --platform esp32
./scripts/test.sh examples --platform esp8266
./scripts/test.sh examples --platform esp32
./scripts/test.sh compile --platform esp32_3_3_11
./scripts/test.sh packages --platform esp32_3_3_11
./scripts/test.sh examples --platform esp32_3_3_11
```
The first two commands compile the library test suites with `test_build_src = yes`. The example commands compile every standalone project on each target, protecting the code that the documentation links users to. CI runs the library target checks on the maintained branch and pull requests.
`esp32` is the explicit Arduino-ESP32 3.0.5 compatibility lane.
`esp32_3_3_11` uses pioarduino `55.03.311` (Arduino-ESP32 3.3.11 / ESP-IDF
5.5.5) as the current validation baseline. The three `compile` commands
compile the complete suites with `test_build_src = yes`; the example commands
compile every standalone project on each target, protecting the code that the
documentation links users to. CI runs every listed target lane on the
maintained branch and pull requests.
The current lane is isolated by the script in a dedicated Core/cache directory
so the package-form Arduino-ESP32 Core 3.3.11 uploader cannot inherit legacy 3.0.5 Python
metadata. `packages` prints the resolved package graph after the current build;
it is a verification step, not a request to change a compiler pin.
The standalone examples are buildable PlatformIO projects; see [examples](../examples/README.md).