-
Notifications
You must be signed in to change notification settings - Fork 3k
Unify mbed OS tools testing style with what's used in mbed-ls, htrun, greentea #4984
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
9983821
Start collecting coverage data in travis
theotherjimmy 177fb79
Rework config_test to use py.test
theotherjimmy de9f9dd
Convert memap tests to pytest style
theotherjimmy 817eb5a
Unify configuration testing and the travis command
theotherjimmy a2bcae0
Rework test_api testing and fix a bug
theotherjimmy 4a937fe
Linting and correcting comments
theotherjimmy b0501bd
Post coverage details on coveralls and link to them in readme
theotherjimmy 399b6ac
Clean up json
theotherjimmy 9d0e8ab
Rename and simplify config test target names
theotherjimmy 6bf7718
Correct travis coverage reporting
theotherjimmy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
{ | ||
"test_target": { | ||
"lib1.p1": "v_p1_lib1_app", | ||
"lib1.p2": "v_p2_lib1", | ||
"lib1.p3": "v_p3_lib1", | ||
"lib2.p1": "v_p1_lib2_app", | ||
"lib2.p2": "v_p2_lib2" | ||
} | ||
} |
File renamed without changes.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
{ | ||
"K64F": { | ||
"exception_msg": "not found" | ||
} | ||
} |
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
{ | ||
"inherits_diamond": { | ||
"target.base1_1": "v_base1_1_f", | ||
"target.base1_2": "v_base1_2_b2", | ||
"target.base1_3": "v_base1_3_b1", | ||
"target.derived1": "v_derived1_d1", | ||
"target.derived2": "v_derived2_f", | ||
"target.base2_1": "v_base2_1_f", | ||
"target.base2_2": "v_base2_2_b2", | ||
"target.f1_1": "v_f1_1_f_override", | ||
"target.f1_2": "v_f1_2_f" | ||
}, | ||
"right_middle": { | ||
"target.base1_1": "v_base1_1_b1", | ||
"target.base1_2": "v_base1_2_b2", | ||
"target.base1_3": "v_base1_3_b1", | ||
"target.base2_1": "v_base2_1_b2", | ||
"target.base2_2": "v_base2_2_b2" | ||
} | ||
} |
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
Oops, something went wrong.
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.
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.
formatting a bit off here
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.
Actually, no. That's correct formatting.
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.
Ahh it just looks weird with config not lining up with patch, but looking more closely I can see the rationale..