Clojure Mutation Testing & Quality FAQs

Name: Clojure Mutation Testing & Quality
Author: metabase

Question 1

How does this skill handle private functions?

Accepted Answer

It follows best practices by testing private functions through their public entry points. It identifies which public functions exercise the private code and groups them into a single branch and PR.

Question 2

Does it require specific environment configurations?

Accepted Answer

Yes, it requires a running nREPL connected to the Metabase dev environment, a valid Linear API key in your environment variables, and an authenticated GitHub CLI.

Question 3

What is mutation testing in the context of this skill?

Accepted Answer

Mutation testing involves making small, intentional changes to your Clojure source code to see if your tests fail. If a test doesn't fail, the mutation 'survives,' indicating a gap in your test coverage that this skill helps fill.

Question 4

Can this skill modify my source code directly?

Accepted Answer

While it generates tests, it avoids direct source code modification for documentation. Instead, it uses GitHub's 'suggested changes' feature to propose code improvements like dead code removal for reviewer approval.

Question 5

How does it ensure new tests are effective?

Accepted Answer

After writing a test, the skill uses the REPL to re-run the mutation test for that specific function and verifies that the previously surviving mutations are now killed.

Clojure Mutation Testing & Quality

Clojure Mutation Testing & Quality

Key Features

Use Cases

Key Features

Use Cases