3 ms·

22 assertions in a test is a lot better than 22 separate tests that fail for the same reason.

• bluGill 4y ago
  They are the same. I don't care, as I'll fix them one at a time, and if the fix happens to fix more than one great.
  • mrits 4y ago
    Fixing one at a time like that is a good way to get into an endless cycle. Zoom out a bit and make a plan before you start coding.
    • bluGill 4y ago
      That should be understood wothout saying. Even with a plan I'm going to fix one at a time.
• Jabbles 4y ago
  With 22 separate tests you have the possibility of knowing that only a subset of them fail. Knowing which fail and which pass may help you debug. In Go, in general, tests fail and continue, rather than causing the test to stop early, so you can tell which of those 22 checks failed. Other languages may have the option to do something similar. https://pkg.go.dev/testing#T.Fail https://pkg.go.dev/testing#T.Fail