How do you know your feature is working perfectly in production?
If something breaks in production, how will you know?
Will you wait for a user to report it to you?
What do you do when your staging test results do not reflect current production behavior?
In order to test proactively as opposed to reactively, try testing in production! You will have an increased accuracy of test results, your tests will run faster due to elimination of bad data, and you will have higher confidence before releases. This can be accomplished through feature flagging, canary releases, setting up a proper CI/CD pipeline, and data cleanup.
You will leave this talk with strategies to mitigate risk, to better your understanding of the steps to get there, and to shift your company’s testing culture, so you can provide the best possible experience to your users. At the end of the day, we don't care if your features work in staging, we care if they work in production.
About Talia
Talia Nassi is an international keynote speaker who delivers content on all things testing and quality. She is a developer advocate at [ Ссылка ] where she works closely with engineering teams globally to ship software more efficiently. She is passionate about feature flagging, canary launches, CI/CD, testing in production, and A/B testing. She has spoken at countless conferences internationally, ranging from audiences of 100 to 2000!
Twitter: talia_nassi
