Testing certain behavior in the runtime sometimes requires device failures. This is easy enough to do with the simulated cameras or basic storage devices (e.g., throwing a runtime error after 10 frames have been written), but it means we have to make changes in the code that we don't want to keep in general.
We can approach this in one of two ways:
Explicitly code up failing simulated devices in acquire-driver-common. These would then be part of the pool of devices that a user could select from, perhaps inadvertently.
Expose capability for adding devices to the device manager dynamically.
Testing certain behavior in the runtime sometimes requires device failures. This is easy enough to do with the simulated cameras or basic storage devices (e.g., throwing a runtime error after 10 frames have been written), but it means we have to make changes in the code that we don't want to keep in general.
We can approach this in one of two ways: