# Testing in Production
Talia Nassi
Developer Advocate at Split
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, better your understanding of the steps to get there, and 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.
[*Destination: Automation*](https://konghq.com/events/destination-automation)*Destination: Automation** is a free, digital event exploring ways organizations can embrace automation to make their applications and underlying tech stacks more efficient, secure and resilient.*
**Presentation Deck:**