Add verbose flag to Go test command

[PasanT9]

Purpose

$subject

Summary by CodeRabbit

• Chores
  • Enhanced CI workflow to display verbose test output during integration testing, improving visibility into test execution.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 64022b91-d65a-4a56-9a40-1a261b3291e3

📥 Commits

Reviewing files that changed from the base of the PR and between b108a96 and ac7ba1e.

📒 Files selected for processing (1)

• .github/workflows/main.yaml

---

Walkthrough

A CI workflow configuration update that adds the -v verbose flag to the go test invocation in the integration test pipeline, enabling more detailed test output during automated testing.

Changes

Cohort / File(s)	Summary
CI Workflow Update .github/workflows/main.yaml	Added -v flag to go test command for verbose output; all other test parameters and targets remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A flag so small, yet help so bright,
Verbose logs shed tests in light,
No mystery in failures now,
Every step is plain, I vow!
The CI pipeline hops with glee. 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete, providing only a placeholder "$subject" for the Purpose section and leaving all other required sections (Goals, Approach, User stories, Release note, etc.) entirely empty.	Complete the Purpose section with the actual motivation and fill in other critical sections like Goals, Approach, Release note, and Documentation to meet the repository template requirements.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a verbose flag to the Go test command, which aligns with the single-line modification shown in the summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch PasanT9-patch-1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}