Which approach describes proper test naming and organization?

• A. Descriptive names, grouped by functionality
• B. Tests should be named with random strings
• C. Tests should be scattered across the codebase without structure
• D. Descriptive names, grouped by functionality, use arrange-act-assert structure, and ensure repeatability

Answer: (D)

Proper test naming and organization hinges on making tests readable, maintainable, and reliable. Descriptive names clearly state what behavior is being verified, so you can understand the test’s intent at a glance without inspecting the code. Grouping tests by functionality keeps related tests together near the code they exercise, making it easier to find and reason about all coverage for a feature. Following an arrange-act-assert structure separates setup, the action under test, and the verification, which enhances clarity and reduces confusion about what each part of the test is doing. Ensuring repeatability means tests are deterministic and insulated from hidden dependencies, so they pass consistently no matter the run order or environment. Putting these ideas together gives tests that are easier to write, read, and trust. The other approaches fall short because they either hide intent with vague names, scatter tests without a logical structure, or skip a consistent testing flow and determinism.