No tester wants to hear a developer say, "it works on my machine!" because what is being said is: "since it worked on my development environment I assume it also works on your test environment hence you cannot possibly have found a bug". We know this not to be true, yet we make the same assumption between environments in a later stage: We test our software on staging environments and assume that our test results carry over to production. We are not testing the software in the setting where our users are facing it. To top it off, we spend a considerable amount of money trying to copy production. Managing test environments is often hard, complex and needs a lot of maintenance effort. A lot of people are already using techniques, which take testing into production like Beta Testing, A/B Testing or Monitoring as Testing. We intend to push the envelope a little further and additionally move running automated checks or exploration to the production stage. To do so we need to take several things into consideration, such as making sure test data does not mess up production data and analytics, as well as hiding untested features from customers.
In this talk, Marcel Gehlen will show you some popular techniques for testing in production. He will also present various strategies, which help tackle common constraints faced when testing in production and they'll also provide you with an approach to gradually shift your testing to production.