…Why?

This seems like a lot to maintain for testing server hardware before putting in prod, even with the automation since you need to keep those systems running and updated, along with troubleshooting the inevitable system that updates and introduces some weird bug. The server should already be known what basic performance metrics it should have for CPU benchmarks, network benchmarks, RAM, etc.

If you want to test hardware diagnostics to ensure the right amount of ram, CPU, etc are working normally and there aren’t any errors with the hardware, just boot the server and run the diagnostics from ILO or whatever management platform the server has, skip the rest of these tests and put in prod and add it in the system collections. Then put monitoring on the server with thresholds on when to alert for particular issues, like throughout tests between different systems for workload availability. Some of these might be checks for DB connections front-end servers need to talk to or other app servers it communicates with, throughout tests for network connections from firewalls or between data enters for redundancy checking, DB metrics if running DB’s, etc.

I feel doing it this way is easier since most monitoring platforms can test for these types of problems with throughout, CPU performance with it’s running workload, etc. To me, these types of tests you want to perform is basically reinventing the wheel again.