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

Design review: Design for Test #27

Open
krook opened this issue Jul 8, 2021 · 0 comments
Open

Design review: Design for Test #27

krook opened this issue Jul 8, 2021 · 0 comments

Comments

@krook
Copy link
Member

krook commented Jul 8, 2021

Implement an automated build and test system including unit tests and coverage.

Generally, each feature critical to the design should include unit tests. Ideally, these tests could either be performed in an emulated environment or directly on the hardware using a test harness. Zephyr RTOS includes a test framework that supports this, otherwise, Unity is another common test framework that can be used.

It should be recommended to community developers that new features be introduced with test coverage of some specified minimum threshold, i.e. 70-80% test coverage on new features, in the same PR as the feature.

@krook krook added this to To do in Pyrrha Development via automation Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant