From: Stephen Hemminger <stephen@networkplumber.org>
To: Lukas Sismis <sismis@dyna-nic.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 4/7] test: add flow parser unit tests
Date: Tue, 6 Jan 2026 10:07:05 -0800 [thread overview]
Message-ID: <20260106100705.4a27da00@phoenix.local> (raw)
In-Reply-To: <20260106153838.398033-5-sismis@dyna-nic.com>
On Tue, 6 Jan 2026 16:38:34 +0100
Lukas Sismis <sismis@dyna-nic.com> wrote:
> Add comprehensive unit tests for the flow parser library.
>
> Tests cover:
> - flow_parser_autotest: Tests rte_flow_parser_parse() with various
> flow command strings including create, destroy, validate, query,
> list, and isolate commands. Verifies parsed patterns, actions,
> and attributes match expected values.
>
> - flow_parser_helpers_autotest: Tests the standalone helper functions
> parse_attr_str(), parse_pattern_str(), and parse_actions_str().
> Verifies parsing of attributes, patterns with various item types,
> and action sequences.
>
> Run with: dpdk-test flow_parser_autotest
> dpdk-test flow_parser_helpers_autotest
>
> Signed-off-by: Lukas Sismis <sismis@dyna-nic.com>
> ---
Should add some negative tests to make sure flow_parser doesn't die on bogus inputs.
AI might help in creating more tests.
next prev parent reply other threads:[~2026-01-06 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:38 [RFC PATCH v2 0/7] flow_parser: add shared parser library Lukas Sismis
2026-01-06 15:38 ` [PATCH v2 1/7] " Lukas Sismis
2026-01-06 15:38 ` [PATCH v2 2/7] app/testpmd: integrate shared flow " Lukas Sismis
2026-01-06 15:38 ` [PATCH v2 3/7] examples/flow_parsing: add flow parser demo Lukas Sismis
2026-01-06 15:38 ` [PATCH v2 4/7] test: add flow parser unit tests Lukas Sismis
2026-01-06 18:04 ` Stephen Hemminger
2026-01-06 18:07 ` Stephen Hemminger [this message]
2026-01-06 15:38 ` [PATCH v2 5/7] doc: add flow parser library maintainers Lukas Sismis
2026-01-06 15:38 ` [PATCH v2 6/7] dts: fix invalid f-string syntax in testpmd API Lukas Sismis
2026-01-06 15:38 ` [PATCH v2 7/7] cmdline: include stddef.h before defining offsetof Lukas Sismis
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=20260106100705.4a27da00@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=sismis@dyna-nic.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;
as well as URLs for NNTP newsgroup(s).