Enhance the codebase and test coverage.

cmd/utils/github_test.go

@@ -1,6 +1,7 @@
 package utils
 
 import (
+	"flag"
 	"os"
 	"testing"
 
@@ -21,8 +22,15 @@ func TestCheckLatestRelease(t *testing.T) {
 	assert.Equal(t, "[no GITHUB_TOKEN set]", release, "Should return no token message")
 	assert.False(t, ok, "Should return false when no token is set")
 
-	// We can't reliably test with a token in CI environments
-	// Just verify the no-token case works as expected
+	// Test with token but simulating API error
+	// Set a dummy token that won't work with the GitHub API
+	os.Setenv("GITHUB_TOKEN", "dummy-token")
+	release, ok = CheckLatestRelease()
+	assert.Equal(t, "", release, "Should return empty string on API error")
+	assert.False(t, ok, "Should return false on API error")
+
+	// We can't reliably test the successful API call in unit tests
+	// as it would require a valid GitHub token and network access
 }
 
 func TestUpdatePackage(t *testing.T) {
@@ -38,9 +46,21 @@ func TestUpdatePackage(t *testing.T) {
 	result := UpdatePackage()
 	assert.False(t, result, "Should return false when no token is set")
 
+	// Test with token but simulating API error
+	os.Setenv("GITHUB_TOKEN", "dummy-token")
+	result = UpdatePackage()
+	assert.False(t, result, "Should return false on API error")
+
+	// Create a test flag to simulate test mode
+	if flag.Lookup("test.v") == nil {
+		// This is a hack to simulate the test flag being set
+		// which is used in the UpdatePackage function to skip actual download
+		flag.Bool("test.v", true, "")
+	}
+
 	// We can't fully test the update functionality as it would modify the binary
-	// but we can test the token check logic
+	// but we've tested the token check logic and API error handling
 }
 
 // Note: We're not using mock transports for these tests to avoid
-// adding complexity. The tests focus on the token presence logic.
+// adding complexity. The tests focus on the token presence logic and error handling.