Habilidades golang-testing
📦
golang-testing
v1.4.0 Revisión del contenido r1 Riesgo medio ⚙️ Comandos externos🌐 Acceso a red📁 Acceso al sistema de archivos⚡ Contiene scripts🔑 Variables de entorno
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.
Compatible con: Codex Code(CC)
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Solicitud de agente
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "golang-testing". Review tests that report every price subtest as passing even when the parent fails.
Resultado esperado:
- 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.
Usando "golang-testing". Plan tests for a PostgreSQL order repository without affecting normal unit tests.
Resultado esperado:
- 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.
Usando "golang-testing". Improve tests for a worker pool that may leak goroutines.
Resultado esperado:
- 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.
Auditoría de seguridad
Riesgo mediov1 • 15/10/2026 Abrir el informe versionado
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
Archivos escaneados
1,495
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados
Preocupaciones de seguridad confirmadas (1)
Medio
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.
Factores de riesgo
⚙️ Comandos externos (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
🌐 Acceso a red (6)
📁 Acceso al sistema de archivos (2)
⚡ Contiene scripts (6)
🔑 Variables de entorno (1)
Auditado por: codex
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/samber-golang-testing/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/samber-golang-testing?utm_source=security_passport_badge)Insignia 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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita 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/1Cita 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"
Comparar variantes
2 variantes instalablesCada autor sigue siendo un skill instalable independiente. La variante recomendada se ordena según la evidencia de Skillstore.
Por qué esta variante es la primera
Mayor puntuación de Skillstore
Autor / fuente Puntuación de Skillstore Confianza de la evidencia Uso en Skillstore Actualizado
Joseph OBrien Recomendado
89jobrien-golang-testing
Puntuación de Skillstore 81
Confianza de la evidencia Alto
Uso en Skillstore 26
Actualizado
2026-10-18
samber Actual
samber-golang-testing
Puntuación de Skillstore 70
Confianza de la evidencia Medio
Uso en Skillstore 4
Actualizado
2026-10-16
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: Medio 45
Arquitectura
100
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación
Lo que puedes crear
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.
Prueba estos prompts
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.
Mejores prácticas
- 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.
Evitar
- 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.
Preguntas frecuentes
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.