I enjoyed reading this, you have a great way of explaining things.
You keep it simple, but without losing details.
My personal opinion is that folks should know that having Jest tests that pass does not mean that their web app will work as expected.
A browser is more than just a JavaScript interpreter, and the rendering engines from browsers are more different now than they ever were.
Safari currently has a 20% market share, and it keeps growing. I'd say cross-browser testing is more important and relevant than it ever was.
Here is what happened to us when we didn't have full test coverage in Safari.
TLDR: Jest tests are useful, but you also need to have functional end-to-end tests, that actually perform the actions from the perspective of a real user.
I enjoyed reading this, you have a great way of explaining things.
You keep it simple, but without losing details.
My personal opinion is that folks should know that having Jest tests that pass does not mean that their web app will work as expected.
A browser is more than just a JavaScript interpreter, and the rendering engines from browsers are more different now than they ever were.
Safari currently has a 20% market share, and it keeps growing. I'd say cross-browser testing is more important and relevant than it ever was.
Here is what happened to us when we didn't have full test coverage in Safari.
TLDR: Jest tests are useful, but you also need to have functional end-to-end tests, that actually perform the actions from the perspective of a real user.
Very good point and indeed one should never solely rely on this kind of testing as it's very one-sided