I’m a software test engineer and spend quite a bit of time performing code reviews. One thing I always ask for is proof that the code works - this requires a co

I’m a software test engineer and spend quite a bit of time performing code reviews. One thing I always ask for is proof that the code works - this requires a combination of unit, integration, and e2e tests. Unit tests are great to show that some code works in isolation, and then a few integration tests can cover the functionality. You should at a minimum cover each path through a function with boundary cases, which would be far too much effort to do via integration tests.