Alternatives to mutest-rs

MuJava may suit students and researchers working on Java mutation testing with JUnit test cases.

LittleDarwin suits Java developers who want to check whether a project’s tests detect generated code changes.

Mutant suits Ruby developers using supported test frameworks who want to assess whether tests detect code changes.

It suits Go developers who want to examine how well package tests catch altered code, or compare automatically generated and manually written test suites.

MutPy suits Python developers and software testers who want to check whether their tests detect code changes.

Gambit suits developers working on Solidity projects who want to assess tests or formal specifications by checking whether they catch generated mutants.

pymute suits Python developers who want mutation testing with pytest or tox and can install Rust and Cargo.

It suits Python teams using pytest that want to assess tests around business logic, security-critical code, or financial calculations.

Infection

Infection suits PHP teams who want to measure whether their tests catch code changes and use mutation scores as a build gate.

It suits Swift teams using Xcode or Swift Package Manager who want mutation scores and surviving-mutant reports.

It suits Python developers using pytest who want to check whether their tests catch selected code changes.

It suits teams using compatible mutation-testing frameworks that want online reports, surviving-mutant information, incremental analysis, or repository badges.

Stryker Mutator

Stryker suits development teams using JavaScript, TypeScript, C#, or Scala who want to measure unit-test effectiveness.

It suits R developers who want to find weak assertions in test suites, including suites generated with LLMs.

PIT

PIT suits Java and JVM developers who want to assess whether their tests catch faults, including teams that can focus mutation analysis on changed code.