Heh. I'm writing a custom tool for a security product that pulls configs down and looks for deviations from expected config values. Instead of running the scri

Heh. I'm writing a custom tool for a security product that pulls configs down and looks for deviations from expected config values. Instead of running the script against the client config and validating it works correctly, I thought to myself "Hey, what if I made a sample configuration with known good and bad values, and have a known result output to quickly validate the script's function?" I just invented testing. No, large scale programming and devops is not my primary job. Yes, I have built validation before, but it isn't habit and this is a bespoke project so I didn't think about it at first.