[dpdk-dev] [PATCH v3 3/7] test/crypto: refactor to use sub-testsuites

[Doherty, Declan]

On 23/04/2021 5:18 PM, Ciara Power wrote:
> The existing implementation runs a giant cryptodev testsuite for most
> autotests, which in turns runs one setup function regardless of device.
> 
> This is now broken down into multiple testsuites,
> that are used as sub-testsuites. Each autotest runs a general crypto
> parent test suite, to which the sub-testsuites are added.
> 
> For example, the AESNI_MB test runs "Cryptodev Unit Test Suite",
> which has a setup function only to configure testsuite params.
> Creation of vdevs in the setup function is no longer supported,
> it is expected the user does this when running the app.
> This autotest previously just ran the cryptodev_testsuite,
> but now has the smaller sub-testsuites added to the parent suite instead.
> The same test cases are being run as before.
> 
> The scheduler autotest creates its own parent testsuite with nested
> sub-testsuites, rather than using the cryptodev testsuite mentioned above.
> This is due to it being more complex in execution,
> by requiring setting different modes before running tests.
> The scheduler autotest no longer requires the extra test cases to
> attach/set mode/detach when running the blockcipher test cases for
> each mode. The attach/set mode/detach functionality is now tested in a
> sub-testsuite. When running the sub-testsuites for each mode,
> the attach/set mode/detach happens in the setup and teardown functions
> for that sub-testsuite.
> 
> Signed-off-by: Ciara Power <ciara.power at intel.com>
> 
....
> 

Hey Ciara, can you make sure to detail the new requirement in the unit 
test documentation about the need to create the sw crypto pmds using the 
--vdev EAL arguments.