https://joestead.codes/tags/testing/Recent content in testing on Joe SteadHugoen-gbTue, 02 Jun 2026 22:13:59 +0100https://joestead.codes/posts/testing-with-configuration-dotnet/Tue, 04 Aug 2020 17:00:00 +0100https://joestead.codes/posts/testing-with-configuration-dotnet/<p>When running automated tests, or running things locally, I often want to use a different configuration to what I would run in production. A JSON file often suffices for local development, however this isn&rsquo;t useful for automated tests where I want different configurations for different tests, or if my configuration is dynamic (e.g. I need to spin up a docker container during startup, and I have to get some configuration from that on the fly).</p>https://joestead.codes/posts/testing-in-production-feature-toggling-netcore/Thu, 18 Jun 2020 17:30:00 +0100https://joestead.codes/posts/testing-in-production-feature-toggling-netcore/<p>I&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&rsquo;t break!</p> <p>Of course, the simple solution would be to run two &ldquo;Production Environments&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&rsquo;t make much sense though.</p>