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.

Sign up for GitHub

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

Jump to bottom

e2e: collect common use cases for scenario-based e2e test #562

Closed
qweeah opened this issue Sep 14, 2022 · 2 comments · Fixed by #746
Closed

e2e: collect common use cases for scenario-based e2e test #562

qweeah opened this issue Sep 14, 2022 · 2 comments · Fixed by #746
Labels
E2E testing End-to-end testing related issues or pull requests
Milestone
v1.0.0-rc.1

Comments

@qweeah
Copy link
Contributor

qweeah commented Sep 14, 2022 •
edited
Loading

For now we have below use cases:

OCI Image users:

  • should be able to use oras pushoras command to upload files
  • should be able to use oras manifest fetchoras command to inspect the packed manifest
  • should be able to use oras pull command to pull uploaded files
  • should be able to user oras copy command to copy the OCI image to a new repository

Common ORAS users:
This is pending for #414

  • should be able to use oras login command to login
  • should be able to run docker commands and reuse the oras credential
  • should be able to use oras logout command to logout

ORAS Artifact users:

  • should be able to use oras attach command to create oras artifacts
  • should be able to use oras manifest fetch command to fetch created oras artifacts
  • should be able to use oras discover command to view the attached artifacts
  • should be able to use oras pull command to pull oras artifacts
  • should be able to user oras copy command to copy OCI and attached artifacts to a new repository

Also since scenario-specific E2E tests will execute based on certain local test files. We need to check required image/artifact files into the source code for all the use cases.
@qweeah
Copy link
Contributor Author

qweeah commented Sep 14, 2022

@FeynmanZhou @yizha1 Can you engage oras users to get more valuable scenarios for E2E tests, thanks.

@qweeah qweeah added the E2E testing End-to-end testing related issues or pull requests label Sep 14, 2022
@qweeah qweeah mentioned this issue Sep 14, 2022
Closed
@FeynmanZhou
Copy link
Member

Sure. @qweeah Currently, I can provide a sample that how users use ORAS in the secure supply chain scenario with oras copy, attach, and discover, see this blog for details.

We can continue to investigate and append more user scenarios for E2E testing.

@shizhMSFT shizhMSFT added this to the v0.16.0 milestone Sep 17, 2022
@FeynmanZhou FeynmanZhou modified the milestones: v0.16.0, v0.17.0 Nov 1, 2022
@FeynmanZhou FeynmanZhou modified the milestones: v0.16.1, v1.0.0-rc.1 Jan 3, 2023
@qweeah qweeah mentioned this issue Jan 12, 2023
Merged
shizhMSFT pushed a commit that referenced this issue Jan 13, 2023
@qweeah
test(e2e): add oci artifact spec for common registry users (#746)
9013115 
Resolves #562

Signed-off-by: Billy Zha <jinzha1@microsoft.com>
TerryHowe pushed a commit to TerryHowe/oras that referenced this issue Feb 2, 2023
@qweeah
test(e2e): add oci artifact spec for common registry users (oras-proj…
f1970ec 
…ect#746)

Resolves oras-project#562

Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E2E testing End-to-end testing related issues or pull requests
Projects
No open projects
ORAS-Planning
Status: Done
Milestone
v1.0.0-rc.1
Development

Successfully merging a pull request may close this issue.

test(e2e): add oci artifact spec for common registry users qweeah/oras
3 participants
@qweeah @shizhMSFT @FeynmanZhou