Testing in Production
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, why not test in production?! By testing in production, you will have an increased accuracy of test results, your tests will run faster in production due to elimination of mock/bad data, and you will have a higher confidence before releases. You can accomplish this through feature flagging, continuous delivery, and data cleanup. Only when your end-to-end tests pass in production will you know that your features are truly working. You will leave this talk with answers of how to mitigate risk, better your understanding of the steps to get there, and how to shift your company’s testing culture to provide the best possible experience to your users.
Talia Nassi is a quality-driven Test Engineer at WeWork with a passion for breaking and rebuilding software to be the highest possible quality. She started interning in QA when she was studying at UC San Diego and immediately knew that she had found her calling. From UCSD she was recruited to work at Visa, where she tested the payment processing system for the Prepaid Cards. After Visa, Talia started at WeWork, where she continues to innovate and do what she loves—deliver high quality software!