Gremlins

Visit Website

Introduction

Gremlins is a mutation testing tool for Go. The README says it works well on smallish Go modules, such as microservices, where it helps validate tests, supports TDD and can act as a CI quality gate, and warns that very big modules can take hours.

It uses coverage to mutate only covered code, applies operators such as conditional boundaries, negation, arithmetic and increment changes, and reports killed, lived, not covered and timed-out mutants with efficacy and coverage percentages. Thresholds can fail a build when efficacy drops. The project is still in 0.x releases.

In the quality loop Gremlins checks whether Go tests actually catch behaviour changes.

The source code is at go-gremlins/gremlins on GitHub under the Apache-2.0 licence, with about 463 stars; the most recent commit was on 30 March 2026.

Features

1. Coverage-guided: Mutates covered code only.
2. Operators: Boundaries, negation, arithmetic and more.
3. Efficacy score: Killed versus lived mutants.
4. Thresholds: Fail CI below targets.
5. Config file: YAML configuration.
6. Diff mode: Limit to changed code.

Pros

1. Simple CLI: gremlins unleash runs everything.
2. Free to use: Open source under the Apache-2.0 licence, so the core tool costs nothing to use.
3. Actively maintained: The repository had commits as recent as 30 March 2026.

Cons

1. Large modules are slow: Runs can take hours.
2. Pre-1.0: APIs may change.
3. Limited operators: Fewer than mature JVM tools.

Usage and Links (Example)

go install github.com/go-gremlins/gremlins/cmd/gremlins@latest
gremlins unleash --threshold-efficacy 80

Resources:

• Gremlins website
• GitHub repository

Pricing

Gremlins is free and open source under the Apache-2.0 licence.

Recommended for?

1. Go microservice teams.
2. TDD practitioners checking test strength.

Conclusion

Gremlins makes mutation testing approachable for Go services.

Keep runs scoped to small modules or changed code.

On CheckOps, Gremlins is filed under the Unit testing and Release & CI gates stages. Related tools listed here include StrykerJS, PIT (Pitest), mutmut, Infection, cargo-mutants and Mull. A short trial on a real project, with your own code, data and pipeline, is usually the fastest way to choose between them, because fit matters more than feature lists. Facts here come from the official site, documentation and repository, checked on 11 November 2026.