When developing patchset [1], I found the kvargs test is hard to understand when tried to add some testcase.
So refactor kvargs by: 1. introduce UT suite framework. 2. extract big test_valid_kvargs() to five part. And add myself for voluntary maintenance of the kvargs library. Note: to ensure patch independenct, new API which in patchset [1] are not included in this patchset. [1] https://patchwork.dpdk.org/project/dpdk/cover/20231103073811.13196-1-fengcheng...@huawei.com/ Chengwen Feng (7): app/test: introduce UT suite framework for kvargs app/test: extract basic token count testcase for kvargs app/test: extract without keys testcase for kvargs app/test: extract with keys testcase for kvargs app/test: extract parse list value testcase for kvargs app/test: extract parse empty elements testcase for kvargs maintainers: update for kvargs library MAINTAINERS | 1 + app/test/test_kvargs.c | 256 ++++++++++++++++++++--------------------- 2 files changed, 128 insertions(+), 129 deletions(-) -- 2.17.1
