No. That’s silly and unattainable.

How about you take a sensible approach to writing unit tests?

  • Ask questions about what you should be testing. Code that is:
    • Prone to break
    • Changes a lot
    • In a high traffic part of the app
  • Look at things like mutation testing, like Stryker
  • Remember that test coverage isn’t a number to reach, but one metric in a game of testing effectively
Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now