Today's tip is a bit higher level.

Do you know what Dark Launching is?

Imagine you need to refactor a certain piece of flow to use some new API. You could do it by replacing the old one, hoping that the new flow is well tested and covered. But you could do it differently. Adding the second implementation to the existing one, calling it, and... just ignoring the results. This way, you can battle tested your new implementation, checking for any potential differences between them and seeing if there are no edge cases that you forget about. This is what Dark Launching is.

Quite recently I've came across a .NET package that allows run such experiments and verifying or rejecting them based on data - Scientist.NET. You have to specify old flow and the experiment and Scientist.NET takes care of the rest. It's really easy and straightforward to use this for experimenting with multiple code solutions.

Links 📑: https://martinfowler.com/bliki/DarkLaunching.html
📑https://github.com/scientistproject/Scientist.net

Did you use such technique in your projects? Would you?

#dotnet #tipsoftheday #testing #darklaunch #scientitsnet

---
If you find this useful, consider giving a like & share ❤.