राम्रो परीक्षणहरू लेख्ने — जो विश्वस्त, मर्मत गर्न सकिने र मूल्यवान हुन् — स्थापित सर्वोत्तम अभ्यासहरू अनुसरण गर्छन्। खराब परीक्षणहरू (नाजुक, ढिलो, अस्पष्ट) एक बोझ बन्छन्, जबकि राम्रो परीक्षणहरू दीर्घकालीन मूल्य प्रदान गर्छन्। यी अभ्यासहरू बुझ्नु प्रभावकारी परीक्षणका लागि महत्त्वपूर्ण छ।
राम्रो परीक्षणहरूको विशेषताहरू (FIRST)
text
FAST → run quickly (so they're run often)
INDEPENDENT/ISOLATED → don't depend on each other or order; each sets up its own state
REPEATABLE → same result every time, any environment (no flakiness)
SELF-VALIDATING → clear pass/fail (assertions, not manual inspection)
TIMELY → written with (or before) the code
मुख्य अभ्यासहरू
text
✓ Test BEHAVIOR, not implementation → tests survive refactoring (don't test internals)
✓ ONE concept per test → focused tests; clear what failed when one breaks
✓ CLEAR NAMES — describe what's tested ("returns error when email is invalid")
✓ Arrange-Act-Assert structure → readable, organized
✓ Cover EDGE cases and error conditions (not just the happy path)
✓ Keep tests SIMPLE and readable (tests are documentation; avoid complex logic in tests)
✓ DETERMINISTIC — no reliance on time, randomness, external state, or order (avoid flaky)
✓ DRY but readable — share setup (fixtures), but keep each test clear on its own