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

4C: Software State Machine Tests #33

Closed
kkramer215 opened this issue Jan 7, 2023 · 2 comments · Fixed by #39
Closed

4C: Software State Machine Tests #33

kkramer215 opened this issue Jan 7, 2023 · 2 comments · Fixed by #39
Assignees

Comments

@kkramer215
Copy link
Contributor

This will be built on the foundation of the command line tool in VCU-4A. Its purpose is to validate the state machine task. It is only concerned with the logic (we don’t necessarily care too much about race conditions in the scope of this task). These would essentially be small “unit tests”.

This would help with the vast number of inputs to the state machine and establish some basic but integral regression tests.

Outputs:
Full design doc explaining all design decisions (we want to be very explicit about the capabilities and drawbacks of this simulation)
Be able to do something like ./run_state_tests and either fail or generate a report

@rafguevara14
Copy link
Collaborator

Looks like there is an easier way to do this by injecting car events through the CLI.

Specifically, watch out for the NotifyStateMachineFromISR() in these changes

https://github.com/sfuphantom/vcu-fw/blob/Finalize-VCU-Infrastructure/Diagrams/Threads/threads.svg

@rafguevara14 rafguevara14 linked a pull request Mar 3, 2023 that will close this issue
@rafguevara14 rafguevara14 self-assigned this Mar 3, 2023
@rafguevara14
Copy link
Collaborator

PR is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants