-
Notifications
You must be signed in to change notification settings - Fork 362
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
[propose] Independent e2e test. #1633
Comments
@zhy76 How about taking this work? |
OK! |
@zhy76 Test context infraCurrently, the test context infra is launching ecs from alicloud. I hope to remove the dep.
E2e test context switchingWhen you finish the /cc @sealerio/sealer-maintainers @sealerio/sealer-reviewers |
Issue Description
Let me describe the way how we start e2e tests for sealer.
There are some major problems for such approach of test, and there are some drawbacks in our way of testing.
test apply
as a example. In this test, sealer will pull an online image(registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8) to executeapply
. But I guess theimage
in test should be basical context, which means we'd better build a image before going to apply.Describe what feature you want
I hope we can abandon the dependency for resource of alicloud.
At every e2e test, we start a registry, start some vms(contaienrs). There are basical context for sealer test.
And we build/apply/run over the vms. I think this job is not hard, and there are many available open source tools could help us out.
The text was updated successfully, but these errors were encountered: