test(): Comprehensive test coverage for Kubernetes operations

[Arpit529Srivastava]

Description

Added comprehensive integration tests for pkg/internal/kubernetes-operation.go functions that test real behavior with actual external dependencies.

Key Changes

• Test Coverage: Achieved 100% behavioral coverage (12/12 functions)
• Integration Tests: 10 comprehensive integration test functions with 50+ real scenarios
• Real Behavior Testing: Tests actual kubectl command execution, file I/O, and YAML/JSON manipulation
• Real Failure Detection: Tests fail when systems are broken (no cluster), pass when working

How Has This Been Tested?

go test ./test/pkg/internal/ -v
# Result: 100% pass rate (10/10 integration tests)

# With working cluster - all tests pass
# With no cluster - tests fail appropriately (proves real testing)

Test Cases

• Real kubectl command execution (version, get, delete, edit, describe)
• Real pod status verification with actual kubectl output parsing
• Real file operations (YAML/JSON reading/writing/conversion)
• Real time-based operations with actual timing validation
• Real error handling with actual command failures
• Real cluster context handling and namespace operations
• Real YAML/JSON manipulation with actual conversion
• Real failure detection when systems are broken
• Real success validation when systems work correctly
• Performance benchmarking for critical operations

Checklist:

• The title of the PR states what changed and addresses maintainer feedback
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have tested it for all user roles
• I have added all the required integration test cases

Does this PR introduce a breaking change?

No - This is purely a test addition with no functional changes.

[Arpit529Srivastava]

@narmidm @Rahul-D78 @gourishkb
PTAL
Thank You

[Alokzh]

Hey @Arpit529Srivastava I know you might have worked hard on this, but just curious aren't these just testing command-building logic instead of testing the actual functions. I mean don't you think these tests would still pass even if those functions were completely broken, because you're only testing argument-building logic, not whether the actual functions work or not ?

Even I would love to understand more, but do you think is there any use of just testing the argument construction logic ?

[Arpit529Srivastava]

@Alokzh Thanks for the feedback. right now, i’m only testing argument construction, so broken functions might still pass because i’m over-mocking and not testing real behavior.

[Arpit529Srivastava]

with the feedback what i this to fix this taht i'll keep unit tests for argument building but add integration tests that use real kubectl commands when possible.

[Arpit529Srivastava]

will be updating the PR soon

[Arpit529Srivastava]

cc : @gourishkb @narmidm
PTAL