Sometimes one cannot get the exact same specs on test hardware versus production, yet a rollout depends on simulating system load to shake out issues. Performa

Sometimes one cannot get the exact same specs on test hardware versus production, yet a rollout depends on simulating system load to shake out issues. Performance testing needs a schedule, visibility, timebox, known scope, backout plan, data revert plan, pre- and post-graphs. Schedule. Folks are clearly tagged in a table with times down the side. Visibility. Folks who should know know when it's going to happen, are invited to the session, and are mentioned in the distributed schedule. Timebox. It's going to start at a defined time and end on a defined time. Known scope. Is it going to fulfill an order? How many accounts created? Backout plan. DBA and DevOps on standby for stopping the test. Data revert plan. We know what rows to delete or update after testing. Pretty pictures. You want to show graphs during the test, so that you know what to improve and everyone's time wasn't wasted. Reference: observing successful runs that didn't result in problems later.