-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add --json
tests for repo
and advisory list
commands
#1532
Conversation
The json string values can contain fnmatch patterns. Adding a new step rather than using "stdout matches line by line" because json format contains a lot of brackets that would need to be escaped when the whole line is considered a regex. It would make the expected output hard to read. In addition to that the ordering can vary, this step compares ordered jsons.
e46cfbb
to
15ad5bd
Compare
""" | ||
|
||
|
||
Scenario: Repo list without arguments --json --refresh --quiet |
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.
Is there a reason for this scenario? It seems to be essentially the same as the Repo list without arguments --json
, and I'm not sure why the --refresh and --quiet options are important. Could you clarify their significance?
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.
It was meant to test that <REPOSYNC>
doesn't get into the stdout.
It was really confusing and wrong.
The --quiet
is not needed because its implicitly set by --json
and I have changed it to repo info
because repo list
doesn't need metadata.
I have updated it.
Thank you for catching that.
--json
tests forrepo
andadvisory list
commands