スキル golang-testing
📦
golang-testing
v1.4.0 コンテンツリビジョン r1 中リスク ⚙️ 外部コマンド🌐 ネットワークアクセス📁 ファイルシステムへのアクセス⚡ スクリプトを含む🔑 環境変数
Build Reliable Go Tests
Go test suites can miss edge cases, leak goroutines, and fail unpredictably. This skill guides test design, review, and debugging with concrete Go testing patterns.
対応: Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "golang-testing" from https://skillstore.io/skills/samber-golang-testing.md and its manifest at https://skillstore.io/api/skills/samber-golang-testing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「golang-testing」を使用しています。 Review tests that report every price subtest as passing even when the parent fails.
期待される結果:
- Finding: the assertion helper captures the parent test instead of the current subtest.
- Correction: create the assertion helper inside each subtest.
- Verification: deliberately break one expected result and confirm that the matching subtest reports failure.
「golang-testing」を使用しています。 Plan tests for a PostgreSQL order repository without affecting normal unit tests.
期待される結果:
- Separate database tests with an integration build tag.
- Start a disposable fixture, load the schema, reset records between tests, and close connections during teardown.
- Bind fixture ports to loopback and keep production credentials out of the test environment.
- Cover creation, missing records, user filtering, and database errors.
「golang-testing」を使用しています。 Improve tests for a worker pool that may leak goroutines.
期待される結果:
- Add package-level goroutine leak checks and verify shutdown after queued work completes.
- Coordinate workers with explicit synchronization instead of arbitrary delays.
- Run concurrent access tests with race detection and keep each test independently runnable.
セキュリティ監査
中リスクv1 • 2026/10/15 バージョン別レポートを開く
All 135 static alerts are false positives involving documentation, Go syntax, mocks, or explicit test operations. A separate integration fixture exposes weakly authenticated PostgreSQL and unauthenticated Redis through unrestricted host port bindings. No evidence found of malicious intent, credential exfiltration, or security-review prompt injection.
9
スキャンされたファイル
1,495
解析済み行数
0
レビュー項目
0
誤検知を無視
確認済みのセキュリティ上の懸念 (1)
中
Test Services Exposed Through Unrestricted Host Ports
The fixture publishes PostgreSQL as "5433:5432" and Redis as "6380:6379" without loopback bindings. PostgreSQL uses test/test credentials, and Redis has no configured authentication. Reachable hosts could access or alter fixture data when these examples run.
Both published port mappings omit a host address, and the service configuration shows weak or absent authentication. Actual remote reachability depends on host networking and firewalls.
リスク要因
⚙️ 外部コマンド (50)
evals/evals.json:6 evals/evals.json:31 evals/evals.json:40-56 evals/evals.json:56-69 evals/evals.json:69-85 evals/evals.json:85 evals/evals.json:110 evals/evals.json:139 evals/evals.json:148-164 evals/evals.json:164 evals/evals.json:173 evals/evals.json:189 evals/evals.json:190-202 evals/evals.json:202-214 evals/evals.json:214-243 evals/evals.json:243 evals/evals.json:268 evals/evals.json:297 evals/evals.json:318-322 evals/evals.json:322-330 evals/evals.json:330-363 evals/evals.json:363 references/http-testing.md:16-21 references/http-testing.md:21-41 references/integration-testing.md:103 references/integration-testing.md:124 SKILL.md:3 SKILL.md:28 SKILL.md:30 SKILL.md:34 SKILL.md:36 SKILL.md:39 SKILL.md:43 SKILL.md:51 SKILL.md:52 SKILL.md:54 SKILL.md:56 SKILL.md:69-75 SKILL.md:75-77 SKILL.md:77 SKILL.md:79-85 SKILL.md:85-87 SKILL.md:87 SKILL.md:89 SKILL.md:93-99 SKILL.md:99-105 SKILL.md:105-143 SKILL.md:143-147 SKILL.md:147 SKILL.md:149-150
🌐 ネットワークアクセス (6)
📁 ファイルシステムへのアクセス (2)
⚡ スクリプトを含む (6)
🔑 環境変数 (1)
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/samber-golang-testing/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/samber-golang-testing?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/samber-golang-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/samber-golang-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
samber. (2026). golang-testing security audit report (audit version 1) [Author version 1.4.0]. Skillstore. https://skillstore.io/skills/samber-golang-testing/audits/1BibTeX形式の引用
@techreport{samber-samber-golang-testing-2026,
author = {samber},
title = {golang-testing security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-testing/audits/1},
note = {Author version 1.4.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-testing security audit report (audit version 1)"
version: "1.4.0"
type: report
authors:
- name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-testing/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-testing:audit:1"
description: "Skillstore immutable audit report identifier"
バリアントを比較
インストール可能なバリアント 2 件各作者のスキルは個別のインストール項目として維持されます。推奨バリアントは Skillstore の証拠で順位付けされます。
このバリアントが首位の理由
Skillstore スコアが最高
作者 / ソース Skillstore スコア 証拠の信頼度 Skillstore 利用状況 更新済み
89jobrien-golang-testing
Skillstore スコア 81
証拠の信頼度 高
Skillstore 利用状況 26
更新済み
2026-10-18
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 45
アーキテクチャ
100
保守性
87
コンテンツ
65
コミュニティ
91
仕様準拠
作成できるもの
Add Unit Coverage
Create named subtests for public functions, boundary inputs, and error paths without coupling tests to private fields.
Review Test Reliability
Inspect pull request tests for assertion scope errors, shared mutable state, timing dependencies, and missing race checks.
Organize Integration Testing
Plan build-tagged database suites with fixture setup, per-test cleanup, and isolated test services.
これらのプロンプトを試す
Write Your First Table-Driven Test
Write named table-driven tests for [function]. Cover normal inputs, empty inputs, boundary cases, and documented errors. Assert observable results.
Test an HTTP Handler
Test [handler] using request and response recorders. Cover valid requests, malformed bodies, missing authentication, and validation errors. Assert status, headers, and response content.
Debug Concurrent Test Failures
Investigate flaky tests in [package]. Check shared state, goroutine cleanup, assertion scope, and timing dependencies. Propose deterministic tests and race detection commands.
Audit a Large Test Suite
Audit [repository] for unit coverage gaps, integration isolation, and goroutine risks. Separate findings by concern. Prioritize fixes with evidence and focused tests. Require disposable databases and loopback-only services.
ベストプラクティス
- Assert public behavior with named cases, including boundary inputs and failure paths.
- Use disposable fixtures, loopback-only services, and explicit cleanup for integration tests.
- Match examples to your Go version and run focused tests before expanding coverage.
回避
- Treating a high coverage percentage as proof that assertions are correct.
- Sharing mutable fixtures, relying on execution order, or using arbitrary sleeps for synchronization.
- Running destructive fixture cleanup against shared databases or exposing test services to untrusted networks.
よくある質問
Which assistants can use this skill?
The declared supported tools are Codex and Claude Code. The guidance targets Go projects.
Does the skill run tests by itself?
No. It provides instructions and examples that an assistant can apply using your project tools and execution permissions.
Which dependencies are required?
Go is required for execution, and gotests supports scaffolding. Testify, goleak, clockwork, and Docker Compose are needed only for relevant examples.
Can integration tests stay separate from unit tests?
Yes. The skill recommends integration build tags and separate test commands, with fixture setup and cleanup.
Will the examples work with every Go version?
No. Check version-specific APIs against your installed compiler and module target before adopting an example.
Are the container fixtures secure without changes?
No. Restrict published ports to loopback or remove them. Replace weak credentials and enable authentication when services need network access.