Concept questionEasy~5 min

Interview question

What qualities make a unit test worth keeping?

What makes a unit test valuable?

Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A valuable unit test protects one observable behavior, runs quickly and deterministically, and fails with a clear reason. It uses representative boundary cases rather than only the happy path. The arrangement should make the business rule understandable, while assertions focus on outcomes instead of private fields or helper calls.

Full answer below

Practice focus

Behavioral contracts, determinism, boundary cases, readability, failure signal, and refactor safety.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
The useful distinction is not whether a test is short; it is whether the test gives clear, durable evidence about behavior the team cares about.
A valuable unit test protects one observable behavior, runs quickly and deterministically, and fails with a clear reason. It uses representative boundary cases rather than only the happy path. The arrangement should make the business rule understandable, while assertions focus on outcomes instead of private fields or helper calls.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I prefer examples that separate important decisions: values just below and above a limit, missing input, duplicate input, and failure behavior. The test name should describe the scenario and result. Parameterized tests are useful when several inputs express one rule, but I split cases when they need different explanations. A test that survives an internal refactor while catching a changed rule is doing useful work.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I also look at maintenance economics. Coverage percentage cannot tell me whether assertions are meaningful, so I use mutation results, escaped defects, and review experience as stronger signals when available. Time, random values, static state, and concurrency should be controlled explicitly. If setup dominates every test, that may reveal an object or responsibility that is too difficult to use, not merely a need for a larger helper.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Testing private methods directly.
Asserting every property regardless of relevance.
Using one giant test for several rules.
Depending on the current clock or random data.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

The test passes after the assertion is weakened or removed.
A rename or extraction breaks behavior tests.
Failures reveal no scenario or expected outcome.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How do you choose boundary cases?
When would you use a theory?
What does mutation testing reveal?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

PR Quality

Opening drill

Concept questionEasy~5 min

Interview question

What qualities make a unit test worth keeping?

What makes a unit test valuable?

Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Behavioral contracts, determinism, boundary cases, readability, failure signal, and refactor safety.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
The useful distinction is not whether a test is short; it is whether the test gives clear, durable evidence about behavior the team cares about.
A valuable unit test protects one observable behavior, runs quickly and deterministically, and fails with a clear reason. It uses representative boundary cases rather than only the happy path. The arrangement should make the business rule understandable, while assertions focus on outcomes instead of private fields or helper calls.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I prefer examples that separate important decisions: values just below and above a limit, missing input, duplicate input, and failure behavior. The test name should describe the scenario and result. Parameterized tests are useful when several inputs express one rule, but I split cases when they need different explanations. A test that survives an internal refactor while catching a changed rule is doing useful work.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I also look at maintenance economics. Coverage percentage cannot tell me whether assertions are meaningful, so I use mutation results, escaped defects, and review experience as stronger signals when available. Time, random values, static state, and concurrency should be controlled explicitly. If setup dominates every test, that may reveal an object or responsibility that is too difficult to use, not merely a need for a larger helper.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Testing private methods directly.
Asserting every property regardless of relevance.
Using one giant test for several rules.
Depending on the current clock or random data.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

The test passes after the assertion is weakened or removed.
A rename or extraction breaks behavior tests.
Failures reveal no scenario or expected outcome.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How do you choose boundary cases?
When would you use a theory?
What does mutation testing reveal?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

PR Quality

What qualities make a unit test worth keeping?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper

What qualities make a unit test worth keeping?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper