Skip to content

[TEST] Refactor minkapi server tests#66

Open
takoverflow wants to merge 6 commits intogardener:mainfrom
takoverflow:refactor-test
Open

[TEST] Refactor minkapi server tests#66
takoverflow wants to merge 6 commits intogardener:mainfrom
takoverflow:refactor-test

Conversation

@takoverflow
Copy link
Copy Markdown
Member

@takoverflow takoverflow commented Sep 21, 2025

What this PR does / why we need it:
Refactor minkapi server tests into a uniform, readable format

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

@gardener-robot gardener-robot added needs/review Needs review size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. needs/second-opinion Needs second review by someone else labels Sep 21, 2025
@takoverflow takoverflow changed the title [TEST] Refactor minkapi server "unit" tests [TEST] Refactor minkapi server tests Sep 21, 2025
@takoverflow takoverflow changed the title [TEST] Refactor minkapi server tests [TEST] Refactor minkapi server tests Sep 21, 2025
@takoverflow takoverflow added the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Oct 7, 2025
@github-actions github-actions bot added needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Oct 7, 2025
@takoverflow takoverflow removed the needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Oct 7, 2025
* create function to check for changes to name and namespace
* removed duplicate `GenerateName` from typeinfo
@takoverflow takoverflow marked this pull request as ready for review October 15, 2025 13:13

package store

import (
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There is already a server_test.go in main. This PR does not appear merged with main ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is rebased on top of main, it's not creating a new server_test, just adding the refactored minkapi server tests to the existing file.

@gardener-robot
Copy link
Copy Markdown
Contributor

@aaronfern You have pull request review open invite, please check

@elankath
Copy link
Copy Markdown
Member

@takoverflow due to lots of changes in main, this PR is severely dated. Please let me know if you wish to close this/re-open

@takoverflow
Copy link
Copy Markdown
Member Author

takoverflow commented Nov 13, 2025

I'll close this soon, and create a new PR.

@gardener-ci-robot
Copy link
Copy Markdown

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

  • After 15d of inactivity, lifecycle/stale is applied
  • After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Mark this PR as rotten with /lifecycle rotten
  • Close this PR with /close

/lifecycle stale

@gardener-robot gardener-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 19, 2025
@gardener-ci-robot
Copy link
Copy Markdown

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

  • After 15d of inactivity, lifecycle/stale is applied
  • After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close

/lifecycle rotten

@gardener-robot gardener-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 3, 2026
@aaronfern aaronfern removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 5, 2026
@gardener-prow
Copy link
Copy Markdown

gardener-prow bot commented Jan 13, 2026

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@gardener-prow gardener-prow bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 13, 2026
@gardener-ci-robot
Copy link
Copy Markdown

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 14d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as active with /lifecycle active
  • Mark this PR as fresh with /remove-lifecycle stale
  • Mark this PR as rotten with /lifecycle rotten
  • Close this PR with /close

/lifecycle stale

@gardener-prow gardener-prow bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2026
@gardener-prow gardener-prow bot added the cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. label Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs/review Needs review needs/second-opinion Needs second review by someone else needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants