smsgateway/client_test.go (1)

998-1000: Assert wrapped error context in the failure case.

At Line 998-Line 1000, the error path only checks non-nil. Consider also asserting the expected wrapped message (e.g., "failed to refresh token") so regressions in error context are caught.

Proposed tightening

 import (
 	"context"
 	"io"
 	"net/http"
 	"net/http/httptest"
 	"net/url"
 	"reflect"
+	"strings"
 	"testing"
 	"time"
@@
 			resp, err := client.RefreshToken(context.Background(), tt.refreshToken)
 			if (err != nil) != tt.wantErr {
 				t.Errorf("RefreshToken error = %v, wantErr %v", err, tt.wantErr)
 			}
+			if tt.wantErr && err != nil && !strings.Contains(err.Error(), "failed to refresh token") {
+				t.Errorf("RefreshToken error = %v, expected wrapped context", err)
+			}
 			if !tt.wantErr && !reflect.DeepEqual(resp, tt.want) {
 				t.Errorf("RefreshToken response = %v, want %v", resp, tt.want)
 			}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@smsgateway/client_test.go` around lines 998 - 1000, The test currently only
verifies presence/absence of an error for RefreshToken; tighten it by asserting
the expected wrapped error message when an error is expected: in the test block
around the RefreshToken call (the failing branch where (err != nil) !=
tt.wantErr is checked), if tt.wantErr is true assert that err is non-nil and
that its message contains the expected context (e.g., "failed to refresh token")
— use err.Error() string containment or errors.Is/errors.As if you have a
sentinel or wrapped error type — so regressions that drop the error context are
caught.

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro