Fix Go e2e tests not running in CI

[SteveSandersonMS]

The test.sh script was running go test -run TestX without ./..., so it only looked for tests in the root go/ directory and missed all tests in go/e2e/.

This adds ./... to each go test command so tests in subdirectories are discovered and executed.

[Copilot]

Pull request overview

This PR fixes a critical issue where Go e2e tests in the go/e2e/ directory were not being executed during CI runs. The test script was only looking for tests in the root go/ directory.

Changes:

• Added ./... package pattern to all go test commands to recursively discover and run tests in subdirectories

Comments suppressed due to low confidence (4)

go/test.sh:55

• The package pattern ./... should be placed after all flags for better readability and consistency with Go conventions. While the current syntax works, the idiomatic format is go test -v -run TestIntegration -timeout 60s ./... where all flags come before the package specification.

This issue also appears in the following locations of the same file:

• line 59
• line 47
• line 51
  go/test.sh:59

• The package pattern ./... should be placed after all flags for better readability and consistency with Go conventions. While the current syntax works, the idiomatic format is go test -v -run TestHelpers -timeout 90s ./... where all flags come before the package specification.
  go/test.sh:47
• The package pattern ./... should be placed after all flags for better readability and consistency with Go conventions. While the current syntax works, the idiomatic format is go test -v -run TestClient -timeout 60s ./... where all flags come before the package specification.
  go/test.sh:51
• The package pattern ./... should be placed after all flags for better readability and consistency with Go conventions. While the current syntax works, the idiomatic format is go test -v -run TestSession -timeout 60s ./... where all flags come before the package specification.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.