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

🎨 Refactor integration tests to use ginkgo/gomega/envtest #7

Open
ahmad-ibra opened this issue Jun 11, 2024 · 1 comment
Open

🎨 Refactor integration tests to use ginkgo/gomega/envtest #7

ahmad-ibra opened this issue Jun 11, 2024 · 1 comment
Labels
refactoring Refactoring / tech debt

Comments

@ahmad-ibra
Copy link
Collaborator

Description

The current integration test setup is a little overkill for what its doing. We should remove our integration test libs and use just ginkgo/gomege/envtest instead

@ahmad-ibra ahmad-ibra changed the title Refactor integration tests Refactor integration tests to use ginkgo/gomega/envtest Jun 11, 2024
@TylerGillson TylerGillson changed the title Refactor integration tests to use ginkgo/gomega/envtest 🎨 Refactor integration tests to use ginkgo/gomega/envtest Jun 11, 2024
@TylerGillson TylerGillson added the refactoring Refactoring / tech debt label Jun 11, 2024
Copy link

dosubot bot commented Nov 8, 2024

Hi, @ahmad-ibra. I'm Dosu, and I'm helping the validatorctl team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • Proposal to refactor integration test setup using ginkgo, gomega, and envtest.
  • Aims to simplify the current complex setup.
  • No comments or further activity since the issue was opened.

Next Steps

  • Is this issue still relevant to the latest version of the validatorctl repository? If so, please comment to keep the discussion open.
  • If there is no further activity, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 8, 2024
@TylerGillson TylerGillson removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Refactoring / tech debt
Projects
None yet
Development

No branches or pull requests

2 participants