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

[v3 Follow Up] CI/CD E2E Tests #117

Open
JacobMGEvans opened this issue Aug 7, 2023 · 1 comment
Open

[v3 Follow Up] CI/CD E2E Tests #117

JacobMGEvans opened this issue Aug 7, 2023 · 1 comment

Comments

@JacobMGEvans
Copy link
Contributor

Depending on how we want to approach this, we could make the E2E tests more robust against flakiness and race conditions.

  1. Create separate workflows 1st one uses the Action and deploys test-worker the 2nd only runs on success of 1st workflow and will call the test-worker and check the response for a positive health check (includes the secrets) then cleans up the Workers.

  2. Similar to the first one, except its done in one workflow using Jobs

Cc: @1000hz

@JacobMGEvans JacobMGEvans self-assigned this Aug 7, 2023
@JacobMGEvans JacobMGEvans changed the title [v4 Follow Up] CI/CD E2E Tests [v3 Follow Up] CI/CD E2E Tests Aug 7, 2023
@JacobMGEvans JacobMGEvans added v3 and removed v4 labels Aug 7, 2023
@demosjarco
Copy link
Contributor

For this test, I think it would be a good idea to hook up GitHub's built in dependabot to watch for the wrangler package updates. Then on the PR that dependabot works (before merge), run these tests too to make sure this action works on the latest wrangler version too.

@github-project-automation github-project-automation bot moved this to Untriaged in workers-sdk Sep 28, 2023
@JacobMGEvans JacobMGEvans removed their assignment Oct 6, 2023
@admah admah removed this from workers-sdk Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants