Навыки 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-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «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 • 15.10.2026 Открыть версионный отчет
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_reportЗначок Markdown
[](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/1Цитата BibTeX
@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 Обновлено
Joseph OBrien Рекомендуется
89jobrien-golang-testing
Оценка Skillstore 81
Достоверность доказательств Высокий
Использование в Skillstore 26
Обновлено
2026-10-18
samber Текущий
samber-golang-testing
Оценка Skillstore 70
Достоверность доказательств Средний
Использование в Skillstore 4
Обновлено
2026-10-16
Оценка 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.