Play all audios:
Illia KolodiazhnyiFollow1 min read·May 10, 2017 --
Listen
Share
Hi Mohib. Yes, the simplest example would be any visual component that is placed somewhere on the page. The Unit-test will verify that this component behaves and is rendered properly. But
there still will be a problem with putting several of these components too close to each other, so they overlap.
This kind of problem is pretty common in UI-development. So my statement about integration testing applies mostly to the environments where components are used in lots of different contexts
(like the user interface). And integration testing must verify those contexts.
Again, I’m not implying the uselessness of Unit-testing — it’s still a very good mean of ensuring code quality. But Integration testing goes one level of abstraction higher and helps with
more complicated problems in behaviour of tested components.