-
Notifications
You must be signed in to change notification settings - Fork 33
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 custom image test WD-10108 #732
Conversation
8f5b2f6
to
ea27976
Compare
Signed-off-by: David Edler <david.edler@canonical.com>
606ce43
to
1c92de7
Compare
Signed-off-by: David Edler <david.edler@canonical.com>
import { test } from "./fixtures/lxd-test"; | ||
import { deleteInstance, randomInstanceName } from "./helpers/instances"; | ||
|
||
test("search for custom image and create an instance from it", async ({ |
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.
this test would fail locally I think, maybe we should skip it for dev environment? Or we could setup a shell script to run before the e2e tests kicks off?
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.
Right, this hinges on the availability of the custom image.
I was planning to extend this test to create the custom image from the UI in the next cycle (as we have the item to add support for that on our roadmap). Maybe we can ignore this incompatibility for local test runs for now and manually create the custom image on our dev machines?
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.
Cool sounds good 👍
I see the test run time came down a fair bit, nice! Just one query about running the custom image test locally |
Done
Fixes WD-10108
QA