Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Test runner for embedded devices that only uses the stack. My solution is macro heavy.
Read the
README.mdfor more details. Make sure to start from theREADME.mdat the root of the project.Start from file
embedded_tester_core/src/lib.rsfor trait definition and follow towards assertion implementation.Then, look at
embedded_tester_derive/src/lib.rsfor trait implementation.Finally, see how all of it is put together in
embedded_runner/src/main.rs.Please suggest feedback on
README.mdfiles, and how to make instruction usage clearer.Suggest ergonomic feedback too, and if certain features which are missing are important.