jmrp.io / kleidos

0

[READ-ONLY] Mirror of https://github.com/jmrplens/kleidos. Kleidos — Hardware BLE password manager for ESP32-S3 (M5StickC Plus2, StickS3, M5Stack Gray, T-Deck, Cardputer) jmrplens.github.io/kleidos/

0

kleidos / qa / tools /

at main 6 files

José M. Requena Plens Add explicit IMU comms + register read/write self-test 3w ago

Reorganize QA scripts: add qa/tools/ dev utilities, delete dead/redundant scripts Move the standalone hardware dev-loop utilities (screenshot+video capture, live resource monitor, credential seeding) into qa/tools/ with a README, and repoint doc/qa references. Delete scripts superseded by the pytest QA system or obsolete: hal_smoke_test.py (ported to qa/tests), capture_all_screens*/capture_sticks3 (LVGL-era, ported to test_screenshots), patch_asynctcp_accept (AsyncTCP unused in IDF-pure), and the one-shot migration helpers add_explicit_brief/bulk_fix_includes. Keep ble_host_pairing_test.py: still referenced by the ble-qa-runner agent/skill. Claude-Session: https://claude.ai/code/session_01Y7Cy1HetRp6TZAUAeekN8X

1 month ago

crypto_bench.py

test(crypto): tighten the export-KDF floor assertion and add hwraw to the QA sweep The envelope iteration-floor test now asserts the OWASP 600,000 minimum the export actually ships, and qa/tools/crypto_bench.py sweeps the S3-only hwraw KDFBENCH mode (classic boards report it as a clean skip). Claude-Session: https://claude.ai/code/session_01SLSU3WoYEyX1J7qWXxmyKo

1 month ago

imu_selftest_run.py

Add explicit IMU comms + register read/write self-test Add IImu::selfTest (default reports "no IMU"), implemented in the MPU6886 and BMI270 drivers. It proves the full I2C path in three ordered phases: a WHO_AM_I / chip-id READ, a non-destructive save/write/verify/restore of a safe config register (MPU6886 sample-rate divider 0x19; BMI270 the unused INT2_IO_CTRL pin register 0x54, writable field bits only) to exercise the WRITE path without lasting config drift, and an accel-magnitude data-path check for gravity. Extract the pure pass/fail predicates into imu_selftest.h so both drivers share them and the decision logic stays unit-testable off-hardware (the concrete drivers cannot link natively — MPU6886 needs the RTOS facade, BMI270 the Bosch API), mirroring the classifyImu seam. Add the DEBUG-gated IMURW/IMUSELFTEST console command, native test coverage, and a MAC-verified QA HIL runner.

3 weeks ago

resource_monitor_tui.py

Reorganize QA scripts: add qa/tools/ dev utilities, delete dead/redundant scripts Move the standalone hardware dev-loop utilities (screenshot+video capture, live resource monitor, credential seeding) into qa/tools/ with a README, and repoint doc/qa references. Delete scripts superseded by the pytest QA system or obsolete: hal_smoke_test.py (ported to qa/tests), capture_all_screens*/capture_sticks3 (LVGL-era, ported to test_screenshots), patch_asynctcp_accept (AsyncTCP unused in IDF-pure), and the one-shot migration helpers add_explicit_brief/bulk_fix_includes. Keep ble_host_pairing_test.py: still referenced by the ble-qa-runner agent/skill. Claude-Session: https://claude.ai/code/session_01Y7Cy1HetRp6TZAUAeekN8X

1 month ago

seed_credentials.py

Reorganize QA scripts: add qa/tools/ dev utilities, delete dead/redundant scripts Move the standalone hardware dev-loop utilities (screenshot+video capture, live resource monitor, credential seeding) into qa/tools/ with a README, and repoint doc/qa references. Delete scripts superseded by the pytest QA system or obsolete: hal_smoke_test.py (ported to qa/tests), capture_all_screens*/capture_sticks3 (LVGL-era, ported to test_screenshots), patch_asynctcp_accept (AsyncTCP unused in IDF-pure), and the one-shot migration helpers add_explicit_brief/bulk_fix_includes. Keep ble_host_pairing_test.py: still referenced by the ble-qa-runner agent/skill. Claude-Session: https://claude.ai/code/session_01Y7Cy1HetRp6TZAUAeekN8X

1 month ago

serial_screenshot.py

Gate the fleet and document the on-device set-time UI Claude-Session: https://claude.ai/code/session_01U878bNJtg9bCvAMM8CFKqS

4 weeks ago

README.md

QA developer utilities#

Hands-on, standalone tools a developer runs during implementation to drive a connected Kleidos device over the serial debug console — capture screens, record video, watch live resources, and seed test data. They are deliberately separate from the automated pytest suite (qa/tests/): pytest is for repeatable pass/fail gates, these are for interactive inspection while you iterate.

All three require a device flashed with a *_debug build (the debug serial console, DEBUG_SERIAL_BUTTONS) and talk to it over the USB serial port.

These are dev-loop utilities, not tests. For automated QA (native + HIL, markers, Allure) use the pytest system — see docs/testing/qa-system.md. The reusable capture/parse logic these tools pioneered now also lives, ported, in qa/qa_lib/ for the pytest layer.

Tools#

Tool	Purpose
`serial_screenshot.py`	Capture framebuffer screenshots (RGB565 → PNG) and record video (KVID stream) from the device over serial. The primary screen/video capture utility.
`resource_monitor_tui.py`	Live, Keil-µVision-style terminal dashboard of on-device resources (heap, tasks, timing) streamed over serial.
`seed_credentials.py`	Quickly provision test credentials into the vault over the serial debug console, so you don't hand-enter data each iteration.

Usage#

Each tool is self-documenting; run with --help for the full flag set. Common invocations (adjust --port to your device — the MAC is the reliable identity; see qa/inventory/devices.yaml):

# One screenshot to a PNG
python3 qa/tools/serial_screenshot.py --port /dev/ttyACM0 -o screen.png

# Record device video while you exercise the UI
python3 qa/tools/serial_screenshot.py --port /dev/ttyACM0 --video

# Live resource dashboard
python3 qa/tools/resource_monitor_tui.py --port /dev/ttyACM0

# Seed test credentials
python3 qa/tools/seed_credentials.py --port /dev/ttyACM0

Safety#

Debug builds only. These drive the debug serial console; they do nothing useful against a _release/_secure build (and must never be pointed at a _secure device).
No secrets in the repo. seed_credentials.py provisions test data only — never commit real credentials, and never pass real PINs/passphrases on a command line that lands in shell history.