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
In testfiles, in addition to the outgoing pi msg, we should specify the expected Arduino response. This will allow smoother automated testing.
To this end, it might be cleaner to separate out test file runner logic from the main game loop.
Also, the opcode generator GUI should be updated to include the expected response from the Arduino (where possible; some instructions like requesting current electromagnet position do not have a static response msg, but others do).
The text was updated successfully, but these errors were encountered:
As part of this PR, fix logic so that the message is sent verbatim; don't parse the test message and then send a message accordingly, just send it directly.
In testfiles, in addition to the outgoing pi msg, we should specify the expected Arduino response. This will allow smoother automated testing.
To this end, it might be cleaner to separate out test file runner logic from the main game loop.
Also, the opcode generator GUI should be updated to include the expected response from the Arduino (where possible; some instructions like requesting current electromagnet position do not have a static response msg, but others do).
The text was updated successfully, but these errors were encountered: