Isolate per-device provider state in controller tests - #558
Open
felix-kaestner wants to merge 2 commits into
Open
felix-kaestner wants to merge 2 commits into
felix-kaestner wants to merge 2 commits into
Conversation
felix-kaestner
force-pushed
the
test-suites
branch
from
September 11, 2026 16:02
7114a3a to
1395203
Compare
felix-kaestner
force-pushed
the
test-suites
branch
from
September 11, 2026 16:42
1395203 to
61eebd3
Compare
felix-kaestner
marked this pull request as ready for review
September 11, 2026 16:43
felix-kaestner
force-pushed
the
test-suites
branch
from
September 15, 2026 09:54
c581c92 to
a31e57c
Compare
The test provider was a singleton shared by all controllers. Every test creates a distinct Device via GenerateName, but the provider stored all state (DNS, BGP, NTP, LLDP, etc.) in flat fields on a single struct. This caused state bleed between test suites and intermittent failures. Refactor the test provider into three parts: - DeviceState: per-device mutable state (all resource fields, ConnectFailure, LastRebootTime), each with its own mutex - DeviceStore: shared map of device name to DeviceState, with a StateFor(name) accessor that creates entries on demand - Provider: lightweight per-reconcile instance created by the ProviderFunc factory, capturing the device name during Connect via the new Connection.DeviceName field Add DeviceName to deviceutil.Connection and set it in GetDeviceConnection so the mock provider can identify the device without changing any controller code. Signed-off-by: Felix Kästner <felix.kaestner@sap.com>
Every controller calls GetDeviceByName before the DeletionTimestamp check. If the Device is deleted before a dependent resource completes its finalizer, the resource enters an infinite error-retry loop that creates API server contention and causes flaky test timeouts. Add Eventually waits for dependent resources to be fully deleted before deleting the Device in all AfterEach hooks. Signed-off-by: Felix Kästner <felix.kaestner@sap.com>
felix-kaestner
force-pushed
the
test-suites
branch
from
September 15, 2026 16:39
a31e57c to
d525f71
Compare
Merging this branch changes the coverage (1 decrease, 2 increase)
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The test provider was a singleton shared by all controllers. Every test creates a distinct Device via GenerateName, but the provider stored all state (DNS, BGP, NTP, LLDP, etc.) in flat fields on a single struct. This caused state bleed between test suites and intermittent failures.
Refactor the test provider into three parts:
Add DeviceName to deviceutil.Connection and set it in GetDeviceConnection so the mock provider can identify the device without changing any controller code.