Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Add an e2e for ignite run #412

Merged
merged 4 commits into from
Sep 10, 2019
Merged

Conversation

chanwit
Copy link
Member

@chanwit chanwit commented Sep 8, 2019

Added a simple e2e test for ignite run command. This one is to test under docker / docker-bridge environment. Tests for containerd / cni will be added after #411 get merged.

e2e tests will be used locally at the moment for devs, and later should be with the CI when we could test them in a remote KVM environment.

This PR fixes #391

@chanwit chanwit requested a review from twelho as a code owner September 8, 2019 13:55
@chanwit chanwit changed the title Add e2e ignite run [WIP] Add e2e ignite run Sep 8, 2019
@chanwit
Copy link
Member Author

chanwit commented Sep 8, 2019

kindly ping @stealthybox if this e2e looks make sense to you, I'll continue adding more tests.

@chanwit
Copy link
Member Author

chanwit commented Sep 8, 2019

Please merge #413 before this one.

@chanwit chanwit changed the title [WIP] Add e2e ignite run Add an e2e for ignite run Sep 8, 2019
Copy link
Contributor

@stealthybox stealthybox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After I rebased on master, building a fresh binary results in a passing e2e test.
We should probably incorporate this into the Makefile at some point with a dependency on the ignite binary so that a dev can just make e2e and not worry about the state of their build.

make ignite > /dev/null && echo built ignite
built ignite

sudo IGNITE_E2E_HOME=$PWD $(which go) test ./e2e/. -count 1
ok  	github.com/weaveworks/ignite/e2e	2.271s

sudo dmsetup ls
cryptswap	(253:0)

sudo ctr -n firecracker c ls
CONTAINER    IMAGE    RUNTIME    

docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

I suggested a quick edit.
If you accept it, I think this a great starting point and we can merge it.

P.S: can you run make tidy-in-docker and see if you get the same vendor output?

e2e/run_test.go Outdated Show resolved Hide resolved
@chanwit
Copy link
Member Author

chanwit commented Sep 9, 2019

For the tidy issue, it should be OK for now as I rebased this PR on top of other changes.

To run e2e tests, a dev would go with make e2e.

Makefile Outdated Show resolved Hide resolved
@chanwit chanwit self-assigned this Sep 10, 2019
@chanwit chanwit added the area/testing Issues related to improving testing label Sep 10, 2019
Signed-off-by: Chanwit Kaewkasi <chanwit@gmail.com>
@chanwit chanwit added this to the v0.6.1 milestone Sep 10, 2019
@chanwit chanwit requested review from stealthybox and removed request for twelho September 10, 2019 11:54
@stealthybox stealthybox merged commit 886bb07 into weaveworks:master Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/testing Issues related to improving testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write e2e test cases for ignite run
2 participants