test: Add unit test for lifecycle/pkg/checker/node_checker.go

[gru-agent]

Trigger Info

Trigger Type	Triggered By	Source File	Assignment
Auto Trigger	TestGru	lifecycle/pkg/checker/cri_shim_checker.go	Detail

Summary

Summary

This PR introduces unit tests for the NodeChecker functionality in the checker package. The tests cover the following:

1. TestNodeChecker_Output:

   • Validates the Output method of NodeChecker to ensure it correctly formats and prints the cluster node status based on the provided NodeClusterStatus.

   • Includes scenarios for:

     • All nodes being ready.

     • Some nodes being not ready, with their IPs listed.

2. TestGetNodeStatus:

   • Tests the getNodeStatus function to verify it correctly extracts the node's IP and readiness status from the corev1.Node object.

   • Covers edge cases such as:

     • Nodes with no internal IP.

     • Nodes with no addresses.

     • Nodes in both ready and not-ready states.

These tests improve the reliability and maintainability of the NodeChecker functionality by ensuring its behavior is well-defined and validated.

Coverage

The change in coverage value, such as: 0% -> 50%, indicates that the coverage was 0% before writing the tests and 50% after writing them.

https://web.dev/articles/ta-code-coverage

Type	Change
lines	0% -> 0%
statements	0% -> 0%
functions	0% -> 0%
branches	0% -> 0%

Test Statuses

Status	Change
passed	0 -> 7 🔺
failed	0 -> 0
skipped	0 -> 0
error	1 -> 0 🔻
source	ai

Tip

You can @gru-agent and leave your feedback. TestGru will make adjustments based on your input

Tip

You can @gru-agent rebase to rebase the PR.

Tip

You can @gru-agent redo to reset or rebase before redoing the PR.

Tip

To modify the test code yourself, click here Edit Test Code

[sealos-ci-robot]

🤖 Generated by lychee action

Summary

Status	Count
🔍 Total	2070
✅ Successful	451
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	1617
❓ Unknown	0
🚫 Errors	0

Full action output

Full Github Actions output

[stale]

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.