This is a collection of binary cli tools and bash scripts that do hardware-specific operations. There have only ever been 10 bugs filed against this package, and nearly all are packaging-related (e.g. sync requests.) Thus, this package may see limited benefit of having dep8 tests.
I think the extent of tests should just check installation of a handful of the most commonly used commands
```
test -e /usr/bin/sg_dd
test -e /usr/bin/sg_map
test -e /usr/bin/sg_inq
test -e /usr/bin/sg_read
```
Probably safe to assume that these are representative enough that if they're installed, all the other utilities would be as well.
It's probably unreasonable to assume that the testing environments this runs in will be assured to have any SCSI devices available for the test. But, if that can be guaranteed, then it might be of use to run sg_inq as a basic smoke test.
This is a collection of binary cli tools and bash scripts that do hardware-specific operations. There have only ever been 10 bugs filed against this package, and nearly all are packaging-related (e.g. sync requests.) Thus, this package may see limited benefit of having dep8 tests.
I think the extent of tests should just check installation of a handful of the most commonly used commands
That said, some simple smoke tests for common commands might be of some usefulness, and could be sufficient to close this bug. From looking at https:/ /www.tldp. org/HOWTO/ SCSI-Generic- HOWTO/sg3_ utils.html I might suggest something like:
```
test -e /usr/bin/sg_dd
test -e /usr/bin/sg_map
test -e /usr/bin/sg_inq
test -e /usr/bin/sg_read
```
Probably safe to assume that these are representative enough that if they're installed, all the other utilities would be as well.
It's probably unreasonable to assume that the testing environments this runs in will be assured to have any SCSI devices available for the test. But, if that can be guaranteed, then it might be of use to run sg_inq as a basic smoke test.