Skip to content
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

Hardware simulation script #12

Closed
abeforgit opened this issue Nov 2, 2019 · 3 comments · Fixed by #26
Closed

Hardware simulation script #12

abeforgit opened this issue Nov 2, 2019 · 3 comments · Fixed by #26
Assignees
Labels
beacon-comm Hardware communication component difficulty:medium

Comments

@abeforgit
Copy link
Collaborator

Script to simulate a reasonably realistic hardware setup. Should generate or play back hardware messages and send them to the telraam instance.

@abeforgit abeforgit added beacon-comm Hardware communication component difficulty:medium labels Nov 2, 2019
@ajuvercr
Copy link
Contributor

ajuvercr commented Nov 7, 2019

Is this like an automated test? Or can the script contain some randomness which would mean a human being would have to verify the correctness.

Could you elaborate on what could go wrong in the communication? I'm thinking about disconnects with the beacons, but that may not happen because of ethernet?
This would simulate the runners and beacons could fail to send a message for a runner passing by?

This is pretty dependant on #13 I guess?

@abeforgit
Copy link
Collaborator Author

No randomness in the first instance. We want to test deterministically first, but later we will want randomness.
Beacons can definitely disconnect, ehternet cables are fragile as heck.
Runners can be missed.
TCP Packets could be malformed.

But most importantly, we want to be able to flood the server with messages to stress test it a bit.

@abeforgit
Copy link
Collaborator Author

abeforgit commented Nov 7, 2019

And no this is not dependent on #13 , the beacons will not interact with the API

Just talked with @mcbloch, leave out the stress testing, this will be a separate issue (see #21 )
So just a relatively realistic stream of messages. Don't focus too much on testing error scenarios yet, just a happy simulation to start with

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beacon-comm Hardware communication component difficulty:medium
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants