Obscure Smells.

An Obscure Test is one where a reader cannot tell, from the test method alone, what scenario is set up, what behavior is exercised, and what outcome is expected — because the intent is buried in too much detail, too little context, or logic hidden elsewhere.

A test that uses `if`/`switch`/ternaries, loops, or `try`/`catch` to decide what to run or assert, so its behavior — and whether it verifies anything at all — depends on which branch executes at runtime.

Test Code Duplication is when the same setup, action, or assertion code is copy-pasted across many tests, so a single change forces edits in many places and tests rot into fragile, near-identical copies.

A test hard-codes unexplained numeric literals in its inputs and assertions, hiding what the numbers mean and where they came from.

A test that uses far more code than it needs to state its scenario, burying the one cause-and-effect it verifies under setup boilerplate, irrelevant data, and field-by-field assertions.