-
Notifications
You must be signed in to change notification settings - Fork 1
Integrate unity test framework #24
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
Conversation
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
112b7df
to
cba6e7d
Compare
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
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 good progress :)
As discuss, we can and will refine in next iterations 🦾
test/unit/src/Test_common_includes.h
Outdated
#include <stdbool.h> | ||
|
||
|
||
// project c includes |
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.
Not sure if this test_common_includes.h and test_includes.h is necessary?
I would also try to stick to snake_case o kebak-case if possible for the files which are not required to start with capital case. Or files which do not include cpp classes, which usually use CamelCase.
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.
I fixed the test file name to snake case already, I remove one of the include file test_common_includes.h but kept test_includes.h to include unity header files... We can include only test_includes.h file in all the tests.
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
Signed-off-by: Ramya Subramanyam <ramya.subramanyam@infineon.com>
By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---
CONTRIBUTING.md also tells you what to expect in the PR process.
Description
Provide the information we need to review your PR. What problem does the pull request solve? "Bug fix" is not a good description.
Related Issue
If you opened an issue before creating the PR, point to it here.
Context
What do we need to know about your development environment, tools, target, and so on. Screenshots are always helpful if there is a UI element to this PR.