fix: use actual user id for channel tests

[seefs001]

⚠️ 提交说明 / PR Notice

Important

• 请提供人工撰写的简洁摘要，避免直接粘贴未经整理的 AI 输出。

📝 变更描述 / Description

(简述：做了什么？为什么这样改能生效？请基于你对代码逻辑的理解来写，避免粘贴未经整理的内容)

渠道测试硬编码userid=1修正为读取实际数据

🚀 变更类型 / Type of change

• 🐛 Bug 修复 (Bug fix) - 请关联对应 Issue，避免将设计取舍、理解偏差或预期不一致直接归类为 bug
• ✨ 新功能 (New feature) - 重大特性建议先通过 Issue 沟通
• ⚡ 性能优化 / 重构 (Refactor)
• 📝 文档更新 (Documentation)

🔗 关联任务 / Related Issue

• Closes 不支持mysql多主集群吗 #5093

✅ 提交前检查项 / Checklist

• 人工确认: 我已亲自整理并撰写此描述，没有直接粘贴未经处理的 AI 输出。
• 非重复提交: 我已搜索现有的 Issues 与 PRs，确认不是重复提交。
• Bug fix 说明: 若此 PR 标记为 Bug fix，我已提交或关联对应 Issue，且不会将设计取舍、预期不一致或理解偏差直接归类为 bug。
• 变更理解: 我已理解这些更改的工作原理及可能影响。
• 范围聚焦: 本 PR 未包含任何与当前任务无关的代码改动。
• 本地验证: 已在本地运行并通过测试或手动验证，维护者可以据此复核结果。
• 安全合规: 代码中无敏感凭据，且符合项目代码规范。

📸 运行证明 / Proof of Work

(请在此粘贴截图、关键日志或测试报告，以证明变更生效)

Summary by CodeRabbit

• Bug Fixes

  • Channel testing now correctly resolves and uses the appropriate user ID from request context or defaults to the root user, ensuring accurate channel consumption logging during testing operations.

• Tests

  • Added unit test to verify proper user ID resolution in channel testing scenarios.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

Channel test endpoints now resolve a test user ID from the request context or database, replacing hardcoded user references throughout test execution, logging, and context initialization.

Changes

User-aware channel testing

Layer / File(s)	Summary
User ID resolution logic and test controller/channel-test.go, controller/channel_test_internal_test.go	resolveChannelTestUserID extracts user ID from Gin context or queries the root user from database; unit test verifies context-based resolution.
Core test function user integration controller/channel-test.go	testChannel now accepts a testUserID parameter and uses it for user cache loading, Gin context setup, group lookup, and consumption logging.
Public endpoint user ID propagation controller/channel-test.go	TestChannel endpoint resolves testUserID and passes it to testChannel with error handling; testAllChannels resolves once upfront and passes the user ID to each channel test invocation.

🎯 2 (Simple) | ⏱️ ~10 minutes

🐰 Where user IDs once were frozen in time,
Now context flows through tests so fine,
Each channel test knows who to be—
Root or request, resolved with glee! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: replacing hardcoded user ID 1 with actual user ID in channel tests.
Linked Issues check	✅ Passed	The PR addresses Issue #5093 by using actual user IDs instead of hardcoded values, enabling proper testing with non-sequential IDs from MySQL multi-master setups.
Out of Scope Changes check	✅ Passed	All changes focus on resolving user ID handling in channel tests; no unrelated modifications detected outside the stated objective.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}