I know that back then I was desperately trying to get into testing at my custmers' request. Standing up a test environment was no small task, and all the tutorials we were pointed at just flat didn't work... they were written on people's machines that were already loaded with tons of gems and tools they likely used elsewhere in their career, but that wasn't helpful outside the enclave there.
I even spent some time with Alice once trying to stand up the environment for Vonage Business. We were on the phone for about two hours and on a "from scratch" development systen, freshly installed and nothing previously on it from a dev perspective and we still had not finished getting all the "parts" in. She left me with a list of gems to install (she had to go) and even after following through getting all that in, Beaker would never stand up a SUT, and the docs at the time just were not correct or complete by any measure.
If we're to supply a test environment, the one thing we can take as a hint is just how easy it was to get started with Unit testing on PDK, and then carry that forward to whatever toolset is settled on so any user regardless of skillset can:
1. Install thing
2. Code in said thing
3. Write unit tests for code in said thing
4. Write acceptance tests for code in said thing
5. Get clean output from said thing
I know this sounds like spoon-feeding, and to a large part I guess it could be characterized as such, but if I'm being honest, here we are 15 years later and I cannot truthfully represent that I have ever set up the Beaker environment successfully.... like, ever. And I'm no stranger to Puppet or Puppet-y things, so some part of the toolset or workflow is broken, and I think our core focus is to "un-broken" all those things, making for an easy step into testing for any user.