If you are testing in-house, then you will (hopefully) have the opportunity to run many tests. This gives you the opportunity to shake out your testing process ahead of time and to bring individuals in as needed to look at specific problems.<\/p>\n
If, however, you are using an outside testing resource service or will be running one big test<\/em> on a production system, then it is crucial to have the right people involved in the planning and execution of the test. This list includes:<\/p>\n During the load test, we recommend making live data available during<\/em> the test to all of the participants (e.g. via a web-share of your desktop). This will give them an opportunity to view test data alongside other metrics that they may be monitoring during the test. We use this approach extensively in our testing services and find that it also gives the participants a better view into the testing process that improves their understanding as well as their contribution to the effort.<\/p>\n Each of these groups brings a specific view of a web-based system and a unique set of talents for identifying, diagnosing and fixing the performance problems that are encountered. Your testing results will be more valuable as a result of their involvement.<\/p>\n Chris Merrill, Chief Engineer<\/p>\n","protected":false},"excerpt":{"rendered":" If you are testing in-house, then you will (hopefully) have the opportunity to run many tests. This gives you the opportunity to shake out your testing process ahead of time and to bring individuals in as needed to look at specific problems. Network administrators\n
\nIf, however, you are using an outside testing resource service or will be running one big test on a production system, then it is crucial to have the right people involved in the planning and execution of the test. This list includes:<\/p>\n
\nSystem developers and\/or integrators
\nWeb- and app-server administrators
\nDatabase admins
\nArchitects
\nContent Experts
\n3rd-party services, such as your hosting company<\/p>\n