> I agree that a single validation framework would make cryptodev validation > easier > to discover, document, and maintain, and could eventually allow some common > setup and reporting infrastructure to be shared. > That said, the overlap between the two applications is primarily at the > cryptodev > API level. Their core purposes are quite different. The FIPS validation > application is > focused on CAVP/ACVP workflows, including request/response processing and > conformance testing, whereas Wycheproof is built around externally maintained > JSON test suites with valid/invalid/acceptable result classifications and > different > requirements for asymmetric devices. > While there may be opportunities for code reuse in the future, merging them > today would likely introduce additional dispatcher and lifecycle complexity > with > limited immediate benefit. It could also blur the distinction between > Wycheproof > robustness testing and FIPS conformance validation. > My preference would be to keep them as separate applications for now and > revisit consolidation if we identify a meaningful amount of shared > infrastructure.
The idea is not about code reuse.. But it is to limit the number of example applications. For crypto validation we already have fips_validation as well as dpdk-test. If we move this new app under a folder examples/crypto_validation along with fips_validation, it will make more sense like multi_process example. We cannot just keep on adding new examples for every new way of crypto validation.
