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.

Sign up for GitHub

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

Jump to bottom

Document testing approach #1

Open
rusefillc opened this issue Dec 25, 2021 · 2 comments
Open

Document testing approach #1

rusefillc opened this issue Dec 25, 2021 · 2 comments
Assignees
@rnd-ash
Labels
documentation Improvements or additions to documentation

Comments

@rusefillc
Copy link

How is this firmware tested?

any unit tests of logic layer?
any info on any sorts of simulated hardware?
@rnd-ash
Copy link
Owner

rnd-ash commented Dec 26, 2021

Currently nothing is simulated. However I will be working eventually on a desk testing setup!

At this point in time my testing simply involves driving on private roads using very unfavorable conditions when I want to test something. Otherwise the TCM itself learns in most situation and can report back to me after I drive

@rusefillc
Copy link
Author

rusefillc commented Jan 17, 2022 •
edited
Loading

I was mostly curious about https://github.com/rnd-ash/ultimate-nag52-fw/tree/main/test which mentions unit tests. From my experience some automated testing is very helpful for complex systems and unit tests are amazing first layer of defense prior to any real hardware tests?

@rnd-ash rnd-ash added the documentation Improvements or additions to documentation label Feb 27, 2022
@rnd-ash rnd-ash self-assigned this Feb 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rnd-ash rnd-ash

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rnd-ash @rusefillc