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
As an aid to development (and particularly regression testing) it would be very helpful if the test suite covered more functionality and as more automated.
Goal is to expand the current testing.ipynb to cover all modes using internal timing, and to have the notebook automatically configure an attached scope for the correct acquisition parameters, and to pull a screenshot and display the result. This will hopefully make it much easier to see if waveform outputs have changed due to some change somewhere. For now, measurements use a scope for simple amplitude checks and a phase-frequency detector for confirming phase/frequency changes (independent only, not simultaneous changes in both).
Next is to have some minor functionality to confirm that externally triggered sequences also function as expected without needing to invoke labscript. Full testing of externally triggered sequences can be handles by test experiments in labscript.
Finally, it would be good if the whole suite exercised each command of the firmware at least once (ie debug commands, clock config, etc). This part doesn't necessarily need to be explicit, but rather ensure that each command is used at least once and its output confirmed to be as expected in some way (ie string matching, visual inspection of waveforms, etc).
Over-arching goal is for the suite to be fairly modular to allow easy addition of new test sequences (for working on particular edge cases quickly), relatively easy substitution of different equipment (eg suite should be simple to modify to run with a Tektronix scope), and most importantly not consume too much of our time writing it (ie not an exhaustive test suite, nor heroically automated).
The text was updated successfully, but these errors were encountered:
As an aid to development (and particularly regression testing) it would be very helpful if the test suite covered more functionality and as more automated.
Goal is to expand the current
testing.ipynb
to cover all modes using internal timing, and to have the notebook automatically configure an attached scope for the correct acquisition parameters, and to pull a screenshot and display the result. This will hopefully make it much easier to see if waveform outputs have changed due to some change somewhere. For now, measurements use a scope for simple amplitude checks and a phase-frequency detector for confirming phase/frequency changes (independent only, not simultaneous changes in both).Next is to have some minor functionality to confirm that externally triggered sequences also function as expected without needing to invoke labscript. Full testing of externally triggered sequences can be handles by test experiments in labscript.
Finally, it would be good if the whole suite exercised each command of the firmware at least once (ie debug commands, clock config, etc). This part doesn't necessarily need to be explicit, but rather ensure that each command is used at least once and its output confirmed to be as expected in some way (ie string matching, visual inspection of waveforms, etc).
Over-arching goal is for the suite to be fairly modular to allow easy addition of new test sequences (for working on particular edge cases quickly), relatively easy substitution of different equipment (eg suite should be simple to modify to run with a Tektronix scope), and most importantly not consume too much of our time writing it (ie not an exhaustive test suite, nor heroically automated).
The text was updated successfully, but these errors were encountered: