Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is useful, if the DUT is a USB device, where you are not yet sure, what exactly it is. This allows the test to use the wrapper to communicate with the device, even if it is on the network.
Might also be useful, if you don't yet have a driver for a USB controlled device and want to test it out before upstreaming it.
Checklist
Not sure about the description in usage and development, but I'm currently using it in my labgrid to communicate with a USB device, that has not yet a driver in Labgrid and where I have not yet come around to upstream the driver, because it is a lot of work to make it work reliable.
Have not written any tests, because I think the USB-Port is already tested enough.