<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>feature-toggling on Joe Stead</title><link>https://joestead.codes/tags/feature-toggling/</link><description>Recent content in feature-toggling on Joe Stead</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 02 Jun 2026 22:13:59 +0100</lastBuildDate><atom:link href="https://joestead.codes/tags/feature-toggling/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing in Production with Feature Toggles in .NET Core</title><link>https://joestead.codes/posts/testing-in-production-feature-toggling-netcore/</link><pubDate>Thu, 18 Jun 2020 17:30:00 +0100</pubDate><guid>https://joestead.codes/posts/testing-in-production-feature-toggling-netcore/</guid><description>&lt;p&gt;I&amp;rsquo;ve always been a big fan of testing, and often think about ways to improve the testability of our system. The most effective testing is to test what your users actually use, and that is to test in production. This can be quite a scary thought to some, shipping untested code out to our live system, with real users, and hope it doesn&amp;rsquo;t break!&lt;/p&gt;
&lt;p&gt;Of course, the simple solution would be to run two &amp;ldquo;Production Environments&amp;rdquo; side by side, and use one exclusively for testing, and only once you are satisfied everything is working, push the tested changes across to the other environment. This doesn&amp;rsquo;t make much sense though.&lt;/p&gt;</description></item></channel></rss>