On Sat, May 04, 2024 at 05:14:41PM GMT, Shin'ichiro Kawasaki wrote: > Some of the test cases in nvme test group do the exact same test for two > blkdev types: device type and file type. Except for this difference, the > test cases are pure duplication. It is desired to avoid the duplication. > When the duplication is avoided, it is required to control which > condition to run the test. > > To avoid the duplication and also to allow the blkdev type control, > introduce a new configuration parameter NVMET_BLKDEV_TYPES. This > parameter specifies which blkdev type to setup for the tests. It can > take one of the blkdev types. Or it can take both types, which is the > default. When both types are specified, the test cases are repeated > twice to cover the types. > > Also add the helper function _set_nvmet_blkdev_type(). It sets up > nvmet_blkdev_type variable for each test case run from > NVMET_BLKDEV_TYPES. > > Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@xxxxxxx> Reviewed-by: Daniel Wagner <dwagner@xxxxxxx>
