-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driver test. #475
Comments
@jenshnielsen I am thinking about having a mock, that simply replaces base, and tests if all the instruments at least can be instantiated. |
Yes agreed, have been doing that manually when testing drivers for instruments that I don't have easy access to. Above is just some examples of why we need it |
Making a mock instrument server which receives messages and sends reply's on specified ports on localhost is I think the best option for making being able to run and debug instrument drivers, at least for IP instruments. In this way we can leave the driver unmodified, that is, the driver being tested is exactly the same as the driver that will actually be used. I have made mock instrument server in my PR (#700), but maybe it is a good idea to open a seperate PR specifically for this problem. |
I guess this was dealt with by #859. At least for VISA instruments there is now a standard way of doing this. |
We need some solution (that should have been baked into the base class to begin with) to make sure the drivers are actually valid python.
The text was updated successfully, but these errors were encountered: