It's very well suited to "single artifact" code (a lib, an app with an easy way to drive interaction through a gui, etc...)
It tends to turn into a "testing sandglass" with time (because most of the value of integration tests is also derived from gui/e2e tests.)
Depending on the app, it might makes sense.
Kent C Dodds (author of the poorly named "testing library") is embracing this sandglass shape by calling it the "testing trophy".
Honestly, to me the hardest deterrent to testing are :
* If it's not done from day 1, you end up with that one hard to test piece of code that makes every other piece of code hard to test
* Few people enjoy writing tests (I do, but I reckon I'm part of a minority.)
Do what helps you the most !!
It's very well suited to "single artifact" code (a lib, an app with an easy way to drive interaction through a gui, etc...)
It tends to turn into a "testing sandglass" with time (because most of the value of integration tests is also derived from gui/e2e tests.)
Depending on the app, it might makes sense.
Kent C Dodds (author of the poorly named "testing library") is embracing this sandglass shape by calling it the "testing trophy".
Honestly, to me the hardest deterrent to testing are :
* If it's not done from day 1, you end up with that one hard to test piece of code that makes every other piece of code hard to test
* Few people enjoy writing tests (I do, but I reckon I'm part of a minority.)
Do what helps you the most !!