I am finally getting around to capturing my "dot files" and other setup parameters because I need to re-create my development environment on different hardware and new VMs. As I go through the setup, I am carefully documenting the steps in README.md and also adding functions to a setup script. The script will, I hope, semi-automate or completely automate the large majority of my re-establishing my personal settings. Many developers have great "dot files," setup scripts, & methods in their public github. I am writing my own from scratch because I am enjoying the process, not because I think mine will be better.
While writing tests for my setup script, I decided to write mostly "negative" tests to attack the functions and handle corner cases I have seen fail in others' code (frequently). In my previous job, I was very saddened by the culture of 100% "happy path" tests written exclusively to pass some "test coverage" target but serving almost no real verification pur