-
Notifications
You must be signed in to change notification settings - Fork 0
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
Refactor ci tests #48
base: main
Are you sure you want to change the base?
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
… tests from the top folder
…nvestigating changing traits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool, really like the testing framework you've set up here!
cargo test inside the esp32c3 tests folder
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
MegaLinter has automatically applied linters fixes on this PR. |
and changed imports back to original
@petekubiak @jamessizeland We now have full CI Testing on both ESP32 and Linux with without the FT232H Board. Next PR will be to add Raspberry Pi Pico and STM32. Covering all modern MCUs. Dependabot should also use this testing setup going forward to that any minor dependancy bumps will be verified through the CI. |
Fantastic work, well done! |
Test Bench is now confirmed working!
At the moment the CI will fail for one of the tests as we don't have the hardware. (Bought some more TMAG boards and will install when they arrive) I did find an interesting bug with the integration tests where all the cold start tests would work repeatably without having to do a cold start except from the conversion status register. Because of this, I have turned off this test via a comment. This allows us to test our library in CI repeatably. |
Description
We want to have our CI tests generic such that they can run on multiple hardware targets. This PR is focusing on the refactoring of the tests to suit this requirement. With the end goal being to run our tests in the CI pipeline using the following:
Type of change
Please Tick the options that are relevant.
How Has This Been Tested?
This will be updating our CI so it should be tested using that and individual machines
Hardware In the Loop Tests
Checklist