testland/ginkgo-tests

Configures and runs Ginkgo - Go BDD test framework with `Describe` / `Context` / `It` nesting; `BeforeEach` / `AfterEach` / `JustBeforeEach` / `JustAfterEach` lifecycle; Gomega matchers DSL (`Expect(actual).To(Equal(expected))`); parallel execution via `-p`; focus (`F` prefix) + skip (`P` prefix); `DescribeTable` + `Entry` for parametrized tests; `ginkgo` CLI tool. Use when working with Go on a BDD-style test suite (Kubernetes-ecosystem standard).

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Ginkgo CI integration

Name: testland/ginkgo-tests
Rating: 80 (1 reviews)
Author: testland

Per Ginkgo documentation.

GitHub Actions with coverage

- run: go install github.com/onsi/ginkgo/v2/ginkgo@latest
- run: ginkgo -p --cover --coverprofile=coverage.out --no-focus -r
- uses: codecov/codecov-action@v4
  with: { files: coverage.out }

-p runs specs in parallel across the CPU count.
--cover --coverprofile=coverage.out emits a Go coverage profile.
--no-focus fails the build if any F-prefix specs exist (catches debug-leftover focus).
-r recurses into all packages.

JUnit XML output

For CI systems that ingest JUnit test reports:

ginkgo --junit-report=junit.xml -r

This writes a JUnit-format report that most CI dashboards render as a per-spec pass/fail table.

Gating on focused specs

ginkgo --no-focus errors if the suite contains any focused (F-prefix) specs. Wire it into the CI run so an accidentally committed FDescribe or FIt fails the pipeline instead of silently skipping the rest of the suite.