Integration testing in the staging environment is a pain. One bad commit from a dependency, and all your automated integration tests start failing. Consequently, developers rightly don't want to gate their code pushes on successful integration tests, and integration test results are quickly dismissed as unreliable, and ignored completely. Ephemeral environments change all of that. By using ephemeral environments as a key part of test strategies, not only has John Jenkins succeeded in moving staging dependent integration tests into the build pipeline, but he has also caught and prevented...
John Jenkins
Lead Software Engineer
Disney
John Jenkins has been in the software testing trenches for over 15 years, creating testing solutions for both front-end and back-end testing challenges. With around 10 years experience working with Selenium type solutions, and close to five years working with API and backend automation, he has begun focusing his efforts on solving the broader challenges that all test solutions must deal with. His career has seen him working at companies of all sizes from startups to multi-national corporations, but the testing challenges he faces are largely the same everywhere. He firmly believes that quality is an investment and a choice, and not an afterthought.