How does it handle database testing?

It provides a specific template for the data access layer using Dockertest to manage ephemeral MariaDB containers for reliable integration tests.

What is the four-stage testing lifecycle in this skill?

The skill enforces a logic-based division for every test: Setup (prepare data), Exercise (run code), Verify (check results), and Teardown (clean up).

How should test packages be named according to this skill?

If your package is named 'abc', the testing package must be named 'abc_test' to ensure a clear separation between implementation and test code.

What is the policy on mocks and stubs?

The standards prioritize using stubs over mocks to maintain simplicity, and suggest using monkey patching for global function simulation.

Which frameworks are required for these Go standards?

This skill specifically standardizes the use of Ginkgo as the BDD framework and Gomega as the preferred assertion library.

Golang Testing Standards

Name: Golang Testing Standards
Author: iceleaf916

byiceleaf916

•

Seguridad y Pruebas

Enforces BDD-style unit testing practices and standardizes Golang test structures using Ginkgo and Gomega.

Acerca de

This skill provides a comprehensive framework for Golang unit testing based on Behavior-Driven Development (BDD) principles. It guides developers through the four-stage test lifecycle—Setup, Exercise, Verify, and Teardown—while enforcing strict naming conventions and architectural patterns. By integrating industry-standard tools like Ginkgo and Gomega, alongside integration testing patterns using Dockertest and monkey patching, this skill ensures that your Go codebase maintains consistent, high-quality, and reliable test suites even for complex data-driven applications.

Características Principales

Standardizes test file naming conventions and package-level isolation (abc_test)
Guides the use of test doubles, prioritizing stubs and monkey patching for global functions
Enforces BDD testing patterns using Ginkgo and Gomega assertion libraries
Provides standardized templates for data access layer testing with Docker integration
Implements the structured four-stage testing lifecycle (Setup, Exercise, Verify, Teardown)
2 GitHub stars

Casos de Uso

Standardizing unit testing patterns across a Go-based engineering team
Modernizing legacy Go test suites to follow BDD and clean code principles
Setting up isolated integration tests for database-driven Go services using containers

Acerca de

Características Principales

Standardizes test file naming conventions and package-level isolation (abc_test)
Guides the use of test doubles, prioritizing stubs and monkey patching for global functions
Enforces BDD testing patterns using Ginkgo and Gomega assertion libraries
Provides standardized templates for data access layer testing with Docker integration
Implements the structured four-stage testing lifecycle (Setup, Exercise, Verify, Teardown)
2 GitHub stars

Casos de Uso

Standardizing unit testing patterns across a Go-based engineering team
Modernizing legacy Go test suites to follow BDD and clean code principles
Setting up isolated integration tests for database-driven Go services using containers