[go: up one dir, main page]

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

Remove the need to manually set up testing environment #577

Open
elefeint opened this issue Aug 13, 2021 · 1 comment
Open

Remove the need to manually set up testing environment #577

elefeint opened this issue Aug 13, 2021 · 1 comment

Comments

@elefeint
Copy link
Contributor
elefeint commented Aug 13, 2021

Original issue: Create a script for setting up all needed integration test resources

  • pubsub topics/subscriptions
  • secret manager secret
  • storage buckets
  • ...
@elefeint
Copy link
Contributor Author
elefeint commented Aug 1, 2022

What should probably be done instead to address both test flakes and onboarding is to update the tests to rely on autocreated randomly named resources rather than competing for the same shared resources.

@elefeint elefeint changed the title Create a script for setting up all needed integration test resources Remove the need to manually set up testing environment Aug 1, 2022
prash-mi pushed a commit that referenced this issue Jun 20, 2023
Bumps [reactor-bom](https://github.com/reactor/reactor) from 2020.0.22 to 2020.0.23.
- [Release notes](https://github.com/reactor/reactor/releases)
- [Commits](reactor/reactor@2020.0.22...2020.0.23)

---
updated-dependencies:
- dependency-name: io.projectreactor:reactor-bom
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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

1 participant