Bug Description
`internal/testutil/` contains two files (`testutil.go` and `binary.go`) with shared test helpers including `UniqueNamespace()`, `MustConnect()`, `CleanupNamespace()`, `DefaultVMOpts()`, `WaitForVMRunning()`, `BinaryPath()`, and `RunVirtwork()`. These helpers are used across all integration and E2E tests but have no unit tests themselves. A bug in a helper (e.g., incorrect label generation in `ManagedLabels()`) could cause false passes across the entire test suite.
Steps to Reproduce
- Check for test files corresponding to `internal/testutil/testutil.go` and `internal/testutil/binary.go`
- No `testutil_test.go` or `binary_test.go` files exist
Expected Behavior
Test utility functions should have their own unit tests to validate their behavior, since bugs in helpers propagate as false passes/failures across the entire test suite.
Actual Behavior
No tests exist for the testutil package.
Command
Other
Go Version
Not provided
Deployment Mode
Not provided
Additional Context
Severity: Low
Files:
- `internal/testutil/testutil.go` — no corresponding test file
- `internal/testutil/binary.go` — no corresponding test file
Bug Description
`internal/testutil/` contains two files (`testutil.go` and `binary.go`) with shared test helpers including `UniqueNamespace()`, `MustConnect()`, `CleanupNamespace()`, `DefaultVMOpts()`, `WaitForVMRunning()`, `BinaryPath()`, and `RunVirtwork()`. These helpers are used across all integration and E2E tests but have no unit tests themselves. A bug in a helper (e.g., incorrect label generation in `ManagedLabels()`) could cause false passes across the entire test suite.
Steps to Reproduce
Expected Behavior
Test utility functions should have their own unit tests to validate their behavior, since bugs in helpers propagate as false passes/failures across the entire test suite.
Actual Behavior
No tests exist for the testutil package.
Command
Other
Go Version
Not provided
Deployment Mode
Not provided
Additional Context
Severity: Low
Files: