https://bugs.dpdk.org/show_bug.cgi?id=1375
Bug ID: 1375
Summary: Make limited use of "per testsuite" conf files.
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: dev@dpdk.org
Reporter: pr...@iol.unh.edu
CC: juraj.lin...@pantheon.tech, pr...@iol.unh.edu
Target Milestone: ---
There will be examples of testsuite which require some divserse input on a per
testsuite or environment basis (setting expected baselines for a testsuite in
perf testing is one example). So, we are going to be doing this at some point
anyways, and I think it is okay to do so now with functional tests too if it
can help make testsuites more concise.
I don't want this suggestion to be conflated with our previous discussion about
building a YAML schema and intepreter for taking testsuite parameters and also
python functions and mapping that to a python testsuite. I think it's clear
based on our 1/24 meeting that we are not going in that direction. However, we
probably do need per-testsuite conf files for some (but not all) suites. I
think how we best leverage this can be a discussion point for next week's DTS
meeting.
--
You are receiving this mail because:
You are the assignee for the bug.
