-
Notifications
You must be signed in to change notification settings - Fork 296
Prevents delegate role name as top-level role name #1690
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
jku
merged 4 commits into
theupdateframework:develop
from
kairoaraujo:issue#1558-delegate-roles-name-not-top-level-roles
Nov 29, 2021
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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
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.
Can you please use the dataset defined at line 321
python-tuf/tests/test_metadata_serialization.py
Line 321 in acb201d
and the test function defined in 336
python-tuf/tests/test_metadata_serialization.py
Line 336 in acb201d
instead of defining a
valid_delegationsand a new test function?We aim to group all valid tests related to a specific class in one dataset and test function.
Also, the name
valid_delegationsis not correct.Those are actually cases of
invalid_delegationsas when you callDelegations.from_dict(copy.deepcopy(case_dict))it causesValueErroras you catch it inside your the test function.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 have a concern about how to make sure that the
ValueErroris the correct unit we want.I mean, we test the
ValueErrorraised, but we don't check if the message comes from the part we want to cover.Unless we don't want to go deep in this level, it is ok.
Uh oh!
There was an error while loading. Please reload this page.
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 think this is a more general question that probably is worth adressing.
I think for sure we want to have all invalid tests for
Delegationsin one single place, but I understand what you mean.Maybe we can check the error message and type inside the with?
What do you think @jku?
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.
Yes, indeed. If agreed in checking the type and error message, we can address it in another issue.