[USB TESTS] we should consider removing some of the USB tests from the whitelist

[Jeff Lane ]

Unless there is a compelling reason to leave them, I'd propose removing the following:

usb mouse test
usb keyboard test
usb HDD test

I can think of no situation where USB worked but a mouse or keyboard did not, or a situation where a thumbdrive would work but a HDD would not (except when said HDD was dead to begin with).

We could remove a bit of manual testing that way and still test the actual USB subsystem itself with just USB keys.

[Daniel Manrique (roadmr)]

I'll mark this "Fix Released" as the current UF whitelist has removed the USB keyboard/mouse test; we still have generic keyboard and pointing device tests, and usb/storage-transfer which verifies the USB stack and mass-storage behavior.

[Daniel Manrique (roadmr)]

Er, sorry, I hadn't realized this is not UF-specific, and indeed the test descriptions are still in the job files. However it might be good to have the test definitions in case someone needs to use them. I'll move this to incomplete pending some discussion of whether it's desirable or we should remove those tests altogether. This would probably entail modifying the whitelists that do use them (hint, none in the default checkbox install do).

[Brendan Donegan (brendan-donegan)]

I think this is really an issue for checkbox-certification at the moment. Entirely removing the tests would be overkill and there's 'nothing to be done' in checkbox itself.

[Jeff Lane  (bladernr)]

I don't think it's harmful to leave the job descriptions in there, they don't take up but a few bits. More importantly, I was thinking of this in terms of streamlining the certification testing process.

For UF, we need some sort of manual test, and perhaps to fix that, we could munge the manual insert/remove tests with a basic storage test and flow something like this:

Description: Click Test to start checking your USB ports. When prompted, please follow the onscreen instructions. You will need a USB thumb drive to complete this test.

Click Test -> Script discovers USB ports available -> Prompts user to inset drive into port 1 -> detects insert, runs storage test, prompts user to remove drive -> detects removal, prompts user to insert drive into port 2 -> detects insert, runs storage test, prompts user to remove drive -> repeat until all discovered ports tested -> end test.

For Certification purposes, I think the best solution would be to assume that there is a USB thumb drive plugged into all available USB ports on the SUT, and run the automated USB Storage test which will discover the drives and do basic storage testing against them.

Brendan and I had discussed at UDS buying a LOT of thumbdrives for the labs for this purpose, and I've been working on sourcing those. With a large enough number of drives, we could use this for certification testing as well as leave the thumb drives plugged in permanently and run the automated usb storage test during SRU as well.

If we want to add a manual option to that stream, we could create a manual test that looks for USB ports, prompts the user to insert a usb drive into each open USB port and click Test to verity they're seen by the OS and continue.

Just some thoughts on this...

[Jeff Lane  (bladernr)]

This is partially resolved with an automated USB test.

However, I think we still need to look at perhaps removing the superfluous tests from the various whitelists as mentioned in the OP.