On Writing Software Well #5: Testing without test damage or excessive isolation.

[@ryanbuckley1636]

Thanks for taking the time to make and share this! Cool to see and hear the reasoning

The right number of assertions per test is the number that makes me feel comfortable to fulfill the test I'm writing. I started by following the rule of one assertion per test and, then I realize that I was writing "micro tests" most of the times.

[@guilhermecaraciolo]

Thanks for sharing such a nice content!

[@Stevoo84]

Hey DHH... I would be really interested in seeing how those tests come to live. At which point those are written, what is the thought process when setting them up (i.e. working with existing fixtures), etc. Would be cool to see some screencast focused on that.

[@niravgandhi9196]

Thanks for sharing this! One question. At which stage of development do you guys write tests for a feature? Is it just when the dev looks complete?

[@BibinVenugopal]

Actually it says, you have to write tests first then do the development

[@maxnovee]

And what about third-party integrations? I bet you are using at least one payment provider API, aren't you stubing/mocking anything there?

[@willbarker3707]

It's mentioned in the description - "Mocks and stubs are necessary evils when talking to external services in some cases, but you rarely need them within the boundaries of your own app."