Skip to content
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

E2E test scenario 1 - Starting from an empty directory #5750

Closed
anandrkskd opened this issue May 18, 2022 · 0 comments · Fixed by #5778
Closed

E2E test scenario 1 - Starting from an empty directory #5750

anandrkskd opened this issue May 18, 2022 · 0 comments · Fixed by #5778
Assignees
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/user-story An issue of user-story kind

Comments

@anandrkskd
Copy link
Contributor

anandrkskd commented May 18, 2022

/kind user-story

User Story
As a quality engineer, I want to create e2e tests that involve using all the features to simulate the developer workflow.

Scenario 1 - Start odo init in an empty directory:
Connect to cluster
Run odo init in interactive mode select javascript/nodejs, then take all default values
Expect output to include "Your new component 'my-nodejs-app' is ready in the current directory."

run odo dev
Expect to get the project deployes to the cluster in developer mode, and the application should get running in the cluster, finally it should enter watch mode waiting for changes to files to redeploy automatically.

Make changes to the server.js file and save them.
Verify to get changes pushed to the server, verify that the changes got deployed.

Make additional changes and save again.
Verify that the additional changes got deployed to the cluster.

Exit dev mode

Run odo deploy
Verify that the component was successfully deployed by running odo list

Enter dev mode again

Make additional changes.

Exit dev mode

Run odo deploy
Verify that the additional changes were successfully redeployed.

Undeploy the application form the cluster by running odo delete component.
Expect the command to ask for confirmation to delete the component.
Verify that the command confirms the deletion.
Verify that the component wad deleted from the cluster.

@openshift-ci openshift-ci bot added the kind/user-story An issue of user-story kind label May 18, 2022
@anandrkskd anandrkskd added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label May 18, 2022
@rnapoles-rh rnapoles-rh changed the title E2E tests E2E test scenario 1 Starting form an empty directory May 18, 2022
@rnapoles-rh rnapoles-rh changed the title E2E test scenario 1 Starting form an empty directory E2E test scenario 1 Starting from an empty directory May 18, 2022
@rnapoles-rh rnapoles-rh changed the title E2E test scenario 1 Starting from an empty directory E2E test scenario 1 - Starting from an empty directory May 18, 2022
@anandrkskd anandrkskd moved this to Todo in odo v3-beta1 May 19, 2022
@anandrkskd anandrkskd moved this from Todo to In Progress in odo v3-beta1 May 25, 2022
@anandrkskd anandrkskd mentioned this issue Jun 1, 2022
3 tasks
@anandrkskd anandrkskd moved this from In Progress to For Review in odo v3-beta1 Jun 1, 2022
Repository owner moved this from For Review to Done in odo v3-beta1 Jun 9, 2022
@rm3l rm3l added the v3 label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/user-story An issue of user-story kind
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants