From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 26.11 0/4] extra unit tests for cfgfile library
Date: Mon, 6 Jul 2026 17:23:43 +0100 [thread overview]
Message-ID: <20260706162348.460489-1-bruce.richardson@intel.com> (raw)
There were a few APIs in the cfgfile library which were not being
tested by the unit tests. Add tests to close that, and other, gaps.
Bruce Richardson (4):
test/cfgfile: improve coverage for listing APIs
test/cfgfile: validate config creation APIs
test/cfgfile: verify file modification API
test/cfgfile: test for long lines in file
app/test/test_cfgfile.c | 197 +++++++++++++++++++++++
app/test/test_cfgfiles/line_too_long.ini | 2 +-
2 files changed, 198 insertions(+), 1 deletion(-)
--
2.53.0
next reply other threads:[~2026-07-06 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 16:23 Bruce Richardson [this message]
2026-07-06 16:23 ` [PATCH 26.11 1/4] test/cfgfile: improve coverage for listing APIs Bruce Richardson
2026-07-06 16:23 ` [PATCH 26.11 2/4] test/cfgfile: validate config creation APIs Bruce Richardson
2026-07-06 16:23 ` [PATCH 26.11 3/4] test/cfgfile: verify file modification API Bruce Richardson
2026-07-06 16:23 ` [PATCH 26.11 4/4] test/cfgfile: test for long lines in file Bruce Richardson
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=20260706162348.460489-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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