test: add 13 read-only smoke scenarios across all services#10
Conversation
GitCode (+5): repos-get, pulls-get, issues-comments, users-list-user, users-get GitHub (+4): users-get, users-list-user, pulls-list, pulls-get Forum (+2): topics-list, topics-get (skipped, forum unstable) Jenkins (+2): builds-get, queue-list (skipped, needs configured instance) Smoke result: 19 passed, 0 failed, 7 skipped Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Welcome To opensourceways CommunityHey @TommyLike , thanks for your contribution to the community. Bot Usage ManualI'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands. |
CLA Signature PassTommyLike, thanks for your pull request. All authors of the commits have signed the CLA. 👍 |
Linking Issue Notice@TommyLike , the pull request must be linked to at least one issue. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces several test scenario configuration files in YAML format for the forum, gitcode, github, and jenkins services. These scenarios define command-line arguments, execution timeouts, and various assertions (such as exit codes, stdout/stderr checks, and JSON key validations) to verify the behavior of different service endpoints. Some scenarios are configured to be skipped due to environment instability or setup requirements. There are no review comments, and I have no feedback to provide on these changes.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
CLA Signature PassTommyLike, thanks for your pull request. All authors of the commits have signed the CLA. 👍 |
The GitHub smoke scenarios were running without authentication because SMOKE_GITHUB_TOKEN was not passed from secrets to the workflow env. Public endpoints worked without auth, but GET /user (users-list-user) required authentication and failed with exit code 1. Also add SMOKE_GITHUB_OWNER and SMOKE_GITHUB_REPO for consistency.
CLA Signature PassTommyLike, thanks for your pull request. All authors of the commits have signed the CLA. 👍 |
2 participants
Summary
Add 13 read-only smoke test scenarios, expanding coverage from 9 to 22 scenarios (7 skipped).
New Scenarios
Smoke Result
Coverage Matrix
Generated with Claude Code