The company I am working for has cameras in their products from at least 2 manufacturers, Mightex and ImagingSource. The Mightex legacy cameras were handled by making an ICamera interface class and fleshing it out. So in order to more easily integrate the Imaging Source cameras into the existing App, I plan to create camera classes for these new cameras using the same technique. All peachy.
But in order to write tests for these new classes, I would really prefer to not have to do it with hardware in the loop. I can see various fake functions in the aravis source. Is there some way to create a fake interface, a fake camera (I have the xml for it from arv-test), and register that camera to the fake interface? Then somehow force my unit tests to use this fake interface, discover the camera, etc?
Thanks in advance,
Paul Ourada
BluSkai Systems