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

chore(test): simplifies ginkgo/gomega tests #237

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bartoszmajsak
Copy link
Contributor

This PR simplifies few things in ginkgo/gomega tests:

  • uses ctx propagation instead of TODO
  • sets default timeouts and interval for Eventually checks eliminating
    duplication
  • reworks some assertions to make them easier to read

Signed-off-by: bartoszmajsak [email protected]

Copy link

gitguardian bot commented Jan 9, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic High Entropy Secret faf3733 controllers/authorino_controller_test.go View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@bartoszmajsak bartoszmajsak force-pushed the ctrl-test-improvements branch from 33378aa to faf3733 Compare January 9, 2025 19:46
This PR simplifies few things in ginkgo/gomega tests:

- uses ctx propagation instead of TODO
- sets default timeouts and interval for `Eventually` checks eliminating
  duplication
- reworks some assertions to make them easier to read

Signed-off-by: bartoszmajsak <[email protected]>
@bartoszmajsak bartoszmajsak force-pushed the ctrl-test-improvements branch from faf3733 to 49ed0be Compare January 9, 2025 19:46
@bartoszmajsak bartoszmajsak changed the title chore(test): simplifies ginkgo/gomega testes chore(test): simplifies ginkgo/gomega tests Jan 9, 2025
@bartoszmajsak
Copy link
Contributor Author

bartoszmajsak commented Jan 9, 2025

Not quite sure what to do with GitGuardian - it's an existing code and presumably a made-up hash. Is there a way to mark it as false-positive?

Copy link
Contributor

@KevFan KevFan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Looks good to me 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants