Add "Write components that are easy to test" #52
Conversation
src/guide/write-easy-test.md
Outdated
|
|
||
| ## Build smaller components | ||
|
|
||
| If a component does less, then it will be easier to test. |
There was a problem hiding this comment.
this is an interesting one. sometimes this can go too far, and people write tiny components and unit test those, which is kind of like testing an implementation detail (not really, but you can imagine if someone had 10 components for a form, and tested each one individually, that would not be as useful as 1 test on the form itself).
this is just my opinion though - I don't have a test file for every component, but I try to have tests that cover all of the components (indirectly is fine, like a form). not sure how opinionated we should be here, though.
There was a problem hiding this comment.
I rephrased it to make it read as a suggestion:
"A general rule of thumb is that if a component does less, then it will be easier to test."
| Check out the [Making HTTP requests](../guide/http-requests.md) guide if you are unfamiliar with testing API calls. | ||
| ::: | ||
|
|
||
| Usually, you will perform several HTTP requests throughout your application. From a testing perspective, HTTP requests provide inputs to the component, and a component can also send HTTP requests. |
afontcu
force-pushed
the
write-easy-to-test
branch
from
a544c6c to
6b4837b
Compare
Closes #34