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 the 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.
Check out more articles and videos
BDD & TDD in React
Test Kitchen: A Recipe for Good Tests
Write Tests. Generate UI. Profit!
Panel Discussion: Future of Web Testing
Don’t Try This at Home: Synchronous I/O in Node.js
Can We Double HTTP Client Throughput?
Workshops on related topic
Testing Web Applications Using Cypress
Building a Shopify App with React & Node
Let's Debug Node.js Applications
Securing Node Applications with Automated Security Testing in CI/CD
How to Troubleshoot API Errors and Reduce MTTD/R
Uniform Browser Automation Infrastructure
Want to have access to all events for 4x less?
Vue.js London 2021
20-21 Oct, 2021
React Advanced Conference 2021
22-25 Oct, 2021