Testing

At Level 2, you write basic tests without being asked. You understand that testing isn't separate from your work—it's part of how your work gets done. You begin to think about what could break and how to prove it won't. You may still need help choosing the right type of test or understanding edge cases, but you now include tests as part of most changes.

Key Behaviors

  • Writes unit or integration tests for the features they build
  • Thinks about happy and sad paths when implementing new code
  • Checks coverage reports or test results as part of daily workflow
  • Fixes broken tests they didn't write
  • Reads and reuses existing test patterns in the codebase

Common Struggles

  • May write overly complex or brittle tests
  • Might miss key edge cases or failure conditions
  • May be unsure how to test UI interactions, async flows, or side effects
  • Can focus too much on testing implementation details over behavior

Success Indicators

You know you're successful when you:

  • Write clear, passing tests for most of your changes
  • Proactively ask what needs to be tested (and what doesn't)
  • Catch regressions early through test failures
  • Fix flaky or failing tests when you encounter them

Mindset Shift

From:

"I write tests for my code."

To:

"I write tests that help the team move faster and safer."

Questions to Ask Yourself

  • Does this test actually verify the behavior we care about?
  • Would this test failure help us quickly debug a real issue?
  • Is this test helping reduce risk—or just adding noise?

Build These Habits

  • 1
    Review others' tests to learn patterns and styles
  • 2
    Refactor tests to reduce duplication or improve clarity
  • 3
    Use test names and structure to explain intent
  • 4
    Delete or fix brittle, misleading, or unused tests

Seek Feedback

  • "Would this test help you if something broke here?"
  • "Are these tests overcomplicated or under-scoped?"
  • "Am I focusing on behavior over implementation?"

Signals You're Ready to Level Up

  • Your tests catch issues before others do
  • You simplify or stabilize flaky tests on your own
  • Others rely on your tests to understand behavior

Focus Summary

  • Test to move fast
  • Test to stay safe
  • Your code is better because you test it

At Level 2, testing is part of your professional rhythm. You no longer think of it as extra work—it's just how you build resilient, trustworthy software.