-
Notifications
You must be signed in to change notification settings - Fork 606
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
Introduce V2V VM Import test case #3975
Introduce V2V VM Import test case #3975
Conversation
await click(applyButton); | ||
} | ||
|
||
async save() { |
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 am not big fan of these one-liner functions. IIUC, there is no expectation for additional business logic to be added here in the near future. Simple await click(saveButton);
makes more sense to me.
Similar comment to other functions.
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.
Done
await importWizard.next(); | ||
// Review | ||
await importWizard.confirmAndCreate(); | ||
await importWizard.waitForCreation(); |
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.
Would it make sense to check the result?
This can be added in a follow-up, if complicated now.
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 don't think additional checking errors would be beneficial at the moment.
Currently the function call await importWizard.waitForCreation();
waits for success message, so if the creation fails for some reason, exception will be raised here and we'll have a screenshot taken wit the error.
We could improve it by reading the error message and returning it if VM creation fails, so that we can work with the error in the test function. This could be definitely useful for negative test scenarios.
I would leave it for a separate effort though.
5f3538a
to
ce51817
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mareklibra, rhrazdil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
/hold cancel |
Implemented VM import scenario
Created
kubevirt-v2v
test suite in kubevirt-plugin