With all the attention on #unitTesting, which absolutely has its place in quality #software #development, we must not turn a blind eye to integration and deployment testing.
If your application server is not your dev machine (usually it isn't), then only running a deployment and running the application afterwards will show the gaps and errors.
Containers help reduce the gap between staging and production, and help spin up tried-and-true production servers once testing is complete.
Conversation
Notices
-
André E. Veltstra (aeveltstra@mastodon.social)'s status on Monday, 17-Jun-2019 20:20:24 UTC André E. Veltstra -
André E. Veltstra (aeveltstra@mastodon.social)'s status on Monday, 17-Jun-2019 20:30:17 UTC André E. Veltstra I say this because today I deployed an application suite and was met with errors left and right, caused by ill-configured libraries.
I have deployed these libraries many times. And I have to change the configuration each time. Because that configuration must not wind up in publicly available source control.
It's a step I tend to forget between application suites, due to time passing.
Integration and deployment tests helped catch that omission.
-