This is ok, but we should recognise the limitation in the test: it checks whether the analyser ever sees the expected frequencies or not, but it doesn't check for other issues that could occur (changing frequencies, glitches). To catch all of that would probably need more work to use the generic checker function from hardware_test_tools. Something we should consider in terms of how comprehensive this test needs to be.
I'll add a note to the test code to this effect. Since glitching will be tested using other transports (UA) a basic test here is likely OK. The main thing we are testing is the ability to load an AWB over HID and run it on the target from a win host.
I'll add a note to the test code to this effect. Since glitching will be tested using other transports (UA) a basic test here is likely OK. The main thing we are testing is the ability to load an AWB over HID and run it on the target from a win host.