On Thu, May 18, 2017 at 02:13:07PM +0200, Johannes Thumshirn wrote: > Add a test group for tests of the SCSI generic driver and and > functions common to the SCSI generic driver and it's test cases. > > Signed-off-by: Johannes Thumshirn <jthumshirn@xxxxxxx> > --- > common/sg | 22 ++++++++++++++++++++++ > tests/sg/group | 40 ++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 62 insertions(+) > create mode 100644 common/sg > create mode 100644 tests/sg/group > > diff --git a/common/sg b/common/sg > new file mode 100644 > index 000000000000..30b5089c68f7 > --- /dev/null > +++ b/common/sg > +# TODO: if this test group has extra requirements for what devices it can be > +# run on, it should define a group_device_requires() function. If tests in this > +# group can be run on the test device, it should return zero. Otherwise, it > +# should return non-zero and set the $SKIP_REASON variable. $TEST_DEV is the > +# full path of the block device (e.g., /dev/nvme0n1 or /dev/sda1), and > +# $TEST_DEV_SYSFS is the sysfs path of the disk (not the partition, e.g., > +# /sys/block/nvme0n1 or /sys/block/sda). > +# > +# Usually, group_device_requires() just needs to check that the test device is > +# the right type of hardware or supports any necessary features using the > +# _test_dev_foo helpers. If group_device_requires() returns non-zero, all tests > +# in this group will be skipped on that device. > +# group_device_requires() { > +# _test_dev_is_foo && _test_dev_supports_bar > +# } Leftover TODO, I'll remove it when applying. If we add an sg test that runs on an actual device, we can define group_device_requires().