Last Updated: 2024-04-18

I wrote my first ever batch of Laravel integration tests and, using the confidence from them, showed off "the new way of doings things" to a team that had never used testing before and pushed. Unfortunately the integration tests on my colleagues' machines so they were not impressed.

After some embarrassment, I discovered the issue was a missing composer (PHP) package. This package was installed locally on my machine, but was missing in the source control. Thus the integration tests passed for me, but not for anyone else. This situation could have been avoided by spinning up a machine in the cloud to test each commit based solely on the code as given.

Lessons

• Only rely on the results of integration tests on third party machines, built completely from the code as described in the repo.
• (And/or) spin up a realistic test ENV on your own machine by installing all dependencies from the composer.json to create a clean slate before executing the actual tests.