-
Notifications
You must be signed in to change notification settings - Fork 173
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
Implement tests for the VCH Creation API [specific ci=Group23-Vic-Machine-Service] #6527
Implement tests for the VCH Creation API [specific ci=Group23-Vic-Machine-Service] #6527
Conversation
bf0b75b
to
b277ec4
Compare
9f9e9b9
to
741f5ea
Compare
5fc84e6
to
cdd6d7c
Compare
d416617
to
63191f7
Compare
f7667f3
to
4cc1a61
Compare
77c0e03
to
be08f85
Compare
be08f85
to
fad93c5
Compare
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.
lgtm
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.
lgtm
|
||
*** Test Cases *** | ||
Create minimal VCH | ||
${before}= Count VCHs |
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'm not sure if counting number of VCHs is required here but it may create issue when we have these tests running concurrently. Just FYI.
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.
Good point. I'll remove the counting; I think being able to inspect it is sufficient proof that the VCH was properly created.
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.
Do we have a plan of adding more tests for other create params as well? e.g. syslogs, container-name-convention, etc.
I added verification for the information I could find in |
33d7013
to
2c23714
Compare
2c23714
to
5f837d9
Compare
5f837d9
to
53e8a7b
Compare
62d6ae1
to
1567845
Compare
1567845
to
2faf0a5
Compare
Implement a suite of positive and negative tests for API-based VCH creation. These tests are not intended to be exhaustive; we can use unit tests for that.
Note that these tests only verify the resulting VCHs using
inspect
and do not verify their functionality using docker. That would be desirable validation, but the existingRun Regression Tests
keyword (and related code) isn't currently written in a way that allows it to be used by these tests. Exposing theRun Regression Tests
functionality in a way that more clearly captures the expected set of inputs would be a good first step towards being able to re-use it in this manner.