Testing automation has a reputation for being slow and unreliable, but automated tests which are not run as a part of the CI/CD pipeline are often ignored or written off when they don't pass. If nobody pays attention to the results though, automated tests are not very useful. Any tests which depend on another system will eventually break, unless special care is taken, keeping the addition of integration (or larger) tests to the build pipeline just out of reach. During this session, John Jenkins will show attendees how these larger tests can be reliably automated, so that these tests can be...
Lead Software Engineer
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.