a previous run and the files and environment variables consulted by that run have not changed either, go test will print the previous test output, replacing the elapsed time with the string “(cached).”
written near an original caching execution. By chance I’ve read that code before I actually use the caching strategy. DBDIFBCMFDPWFSQSPpMF .ZpSTUDPOUBDUXJUIUIJTGFBUVSF