I came up with this format 10 years ago to document running our regression test. It was a complicated process (for reasons) and I had four major sections---one

I came up with this format 10 years ago to document running our regression test. It was a complicated process (for reasons) and I had four major sections---one outlining items to do once, such as: [ ] Check you can log into Jenkins [ ] Check you have an account on lab1 [ ] SSH into account on lab1 [ ] "mkdir bin" [ ] "mkdir conf" [ ] "mkdir var" [ ] In shell configuration file, export following [ ] export FOOBAR=... [ ] export PATH=$PATH:$FOOBAR/bin:$FOOBAR/install [ ] export LD_LIBRARY_PATH=$FOOBAR/lib64b:$LD_LIBRARY_PATH [ ] Ensure you can run "sudo -u root foo" [ ] Ensure you can run "sudo -u nobody bar" [ ] Check you have an account on lab 2 [ ] SSH into account on lab2 [ ] ... A second section outlining the steps needed to prepare to run the regression test. The third section was actually running the regression test, and the final section about shutting down the regression test. This list was then checked into our repository and any new hires were given this check list to do (and update it for any steps not clear or not specified---such updates happened a few times). When I came up with this system, I didn't know about ORG mode. Nor did I expect anyone to use a tool other than a text editor with this. Heck, a person could print this out and use a pen to mark items off the list.