From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Jonas Rebmann <jre@pengutronix.de>
Subject: [PATCH 0/7] TLV integration tests and test/py cleanup
Date: Fri, 26 Sep 2025 12:14:01 +0200 [thread overview]
Message-ID: <20250926-tlv-integration-v1-0-45dc68b9b602@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.
Cleanups here and there.
The ci-container needs to be rebuilt before the new tests will succeed
in CI.
Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
---
Jonas Rebmann (7):
test: when testfs feature is available, always enable it
test: provide testfs via fixture
test: move dm-verity testdata generation to fixture
test: py: test_bootchooser: remove dead code
commands: tlv: clarify error opening tlv
ci: container: install crcmod and cryptography
test: py: add TLV integration tests
.github/workflows/test-labgrid-pytest.yml | 3 --
commands/tlv.c | 8 ++--
conftest.py | 14 ++++++
scripts/generate_testfs.sh | 44 -----------------
test/Containerfile | 8 ++--
test/py/test_bootchooser.py | 4 --
test/py/test_dm.py | 53 ++++++++++++++++++--
test/py/test_fit.py | 9 +---
test/py/test_tlv.py | 80 +++++++++++++++++++++++++++++++
9 files changed, 153 insertions(+), 70 deletions(-)
---
base-commit: 7e32be40a193007e138c0eb589eb852420655523
change-id: 20250926-tlv-integration-945bdd7903d9
Best regards,
--
Jonas Rebmann <jre@pengutronix.de>
next reply other threads:[~2025-09-26 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:14 Jonas Rebmann [this message]
2025-09-26 10:14 ` [PATCH 1/7] test: when testfs feature is available, always enable it Jonas Rebmann
2025-09-26 10:14 ` [PATCH 2/7] test: provide testfs via fixture Jonas Rebmann
2025-09-26 10:14 ` [PATCH 3/7] test: move dm-verity testdata generation to fixture Jonas Rebmann
2025-09-26 14:25 ` Jonas Rebmann
2025-09-28 9:54 ` Tobias Waldekranz
2025-09-29 8:29 ` Jonas Rebmann
2025-09-29 7:53 ` Sascha Hauer
2025-09-26 10:14 ` [PATCH 4/7] test: py: test_bootchooser: remove dead code Jonas Rebmann
2025-09-26 10:14 ` [PATCH 5/7] commands: tlv: clarify error opening tlv Jonas Rebmann
2025-09-26 10:14 ` [PATCH 6/7] ci: container: install crcmod and cryptography Jonas Rebmann
2025-09-26 10:14 ` [PATCH 7/7] test: py: add TLV integration tests Jonas Rebmann
2025-09-26 13:57 ` [PATCH 0/7] TLV integration tests and test/py cleanup 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=20250926-tlv-integration-v1-0-45dc68b9b602@pengutronix.de \
--to=jre@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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