You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following on the tests, I'd like to have some tests that I can run on an actual HW device, so not into the unitests infrastructure. That is, very much like a quick test that your HW is working correctly. A bit like the test print page in the brand new printer.
For example, a light_source that does three quick pulses, three short and then ramps up and down in power. Or for the SLM, run a few stripy (visible) patterns and rump up and down the phase in the lines.
This is something that can be useful for development (in fact I use those scripts) but that they can be distributed so someone can plug in the device, run the code and observe that the behaviour is like in some human readable description. Is there a place for this? I see the role of the GUI on this, but the GUI is only going to test what you tell it to test. Maybe one option is to add to the GUI a test button that triggers the test.
The text was updated successfully, but these errors were encountered:
Following on the tests, I'd like to have some tests that I can run on an actual HW device, so not into the unitests infrastructure. That is, very much like a quick test that your HW is working correctly. A bit like the test print page in the brand new printer.
For example, a light_source that does three quick pulses, three short and then ramps up and down in power. Or for the SLM, run a few stripy (visible) patterns and rump up and down the phase in the lines.
This is something that can be useful for development (in fact I use those scripts) but that they can be distributed so someone can plug in the device, run the code and observe that the behaviour is like in some human readable description. Is there a place for this? I see the role of the GUI on this, but the GUI is only going to test what you tell it to test. Maybe one option is to add to the GUI a test button that triggers the test.
The text was updated successfully, but these errors were encountered: