From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Tobias Waldekranz <tobias@waldekranz.com>,
Jonas Rebmann <jre@pengutronix.de>
Subject: [PATCH v2 0/9] TLV integration tests and test/py cleanup
Date: Mon, 29 Sep 2025 10:03:51 +0200 [thread overview]
Message-ID: <20250929-tlv-integration-v2-0-55f75da7e670@pengutronix.de> (raw)
With TLV signature coming up, we want to test all things TLV more
thoroughly, including "roundtrip" integration tests that include the
bareboxtlv-generator python-script and the tlv barebox-command.
As this is the third test module to make use of the testfs, it seemed
adequate to revisit its implementation.
Avoid integration test logic outside pytest; migrate logic from .github/
and scripts/ into pytest.
Use fixtures for testcase preconditions and migrate existing testdata
preparation from scripts/generate_testfs.sh.
Cleanups here and there.
The ci-container needs to be rebuilt before the TLV tests will succeed
in CI.
Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
---
Changes in v2:
- work around a corner case where a failed network test leads to
unrelated pritinting above the tlv command output (triggered by
accessing the 9pfs)
- move fitimage testdata generation to fixture and drop script
- Enable CMD_TLV for multi_v7 and multi_v8 (required for tlv_command test)
- Skip tlv_command test if CMD_TLV is disabled
- Ensure that pwd is returned to / after dm_verity test even on failure
- Silently skip generating testdata for the fit tests for platforms for
which no files are provided to prevent ci failure on mips and riscv
- minor improvements in style and consistency
- Link to v1: https://lore.barebox.org/barebox/20250926-tlv-integration-v1-0-45dc68b9b602@pengutronix.de
---
Jonas Rebmann (9):
test: when testfs feature is available, always enable it
test: provide testfs via fixture
test: move dm-verity testdata generation to fixture
test: move fitimage testdata generation to fixture and drop script
test: py: test_bootchooser: remove dead code
commands: tlv: clarify error opening tlv
ci: container: install crcmod and cryptography
configs: enable tlv command for multi_v7 and multi_v8
test: py: add TLV integration tests
.github/workflows/test-labgrid-pytest.yml | 13 ----
arch/arm/configs/multi_v7_defconfig | 2 +
arch/arm/configs/multi_v8_defconfig | 2 +
commands/tlv.c | 8 ++-
conftest.py | 14 ++++
scripts/generate_testfs.sh | 77 ---------------------
test/Containerfile | 8 ++-
test/py/test_bootchooser.py | 4 --
test/py/test_dm.py | 59 ++++++++++++++--
test/py/test_fit.py | 46 +++++++++++--
test/py/test_tlv.py | 78 ++++++++++++++++++++++
.../testdata}/multi_v7_defconfig-gzipped.its | 0
.../testdata}/multi_v8_defconfig-gzipped.its | 0
13 files changed, 200 insertions(+), 111 deletions(-)
---
base-commit: 1b817ae40c2ba628ba0ce413564ea77e91a6009b
change-id: 20250926-tlv-integration-945bdd7903d9
Best regards,
--
Jonas Rebmann <jre@pengutronix.de>
next reply other threads:[~2025-09-29 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 8:03 Jonas Rebmann [this message]
2025-09-29 8:03 ` [PATCH v2 1/9] test: when testfs feature is available, always enable it Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 2/9] test: provide testfs via fixture Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 3/9] test: move dm-verity testdata generation to fixture Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 4/9] test: move fitimage testdata generation to fixture and drop script Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 5/9] test: py: test_bootchooser: remove dead code Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 6/9] commands: tlv: clarify error opening tlv Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 7/9] ci: container: install crcmod and cryptography Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 8/9] configs: enable tlv command for multi_v7 and multi_v8 Jonas Rebmann
2025-09-29 8:04 ` [PATCH v2 9/9] test: py: add TLV integration tests Jonas Rebmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250929-tlv-integration-v2-0-55f75da7e670@pengutronix.de \
--to=jre@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=tobias@waldekranz.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox