Below is a list of questions that need answering before running a performance test. We recommend that you should follow this list every time you performance test your site.

First, you should begin by defining and recording the performance targets and business requirements for your test.

Note: Preparation during this step requires significant time, and requires information from the appropriate stakeholders of the test. Attention to detail at this stage is of the utmost importance.

Answer the following elements before beginning your testing:

Specify the objective of the test (ex: determine the overall capacity of the application; determine the how the application should perform for a specific peak events)

• What tests will the application undergo?
• How many times will the test run on an application?
• What are the designed workload models for the test?
• Does this workload model address your needs and objectives?
• Will tests address users flows and important key business elements within the application?
• Does testing address your business transaction needs?
• What geographical areas will testing address, and are they the most important locations?
• Will the test address appropriate devices (mobile, tablet, pc, browsers)?

Now that you have a list of the questions that need addressing, you can now begin to set up your performance test.

Below is a list of steps required to begin your performance test:

1. Create a performance test environment in which to conduct your required tests that simulates the actual production environment.
2. Deploy your application onto this environment.
3. Ensure that it is the correct version for testing.
4. Create any required scripts based on the business flows identified for the series of tests.
5. Create test data and load it into the scripts to make test scenarios more dynamic and simulate actual production scenarios.
6. Develop a workflow model.
7. Based on your testing scenario, create a workflow model using scenario generators available in the test tools.
8. Conduct a final environment check before starting your tests.
9. Implement your performance tests and server fixes.
10. Analyze results after all tests have finished running.
11. Note and review important points (anomalies) that arise during the test.
12. Generate a performance test report based on data analysis studies conducted on results.
13. Share reports with technical and business stakeholders.
14. Typical performance test reports include these important elements:
15. A detailed account of response times related to various tests
16. An output of server counters
17. An output of client side counters
18. Any error details
19. Any important conclusions that stem from the conducted performance test
20. A comparison of these tests against earlier tests or tests performed on an earlier version of the product
21. Determine, with stakeholders, and follow-up activities that need action, and set new objectives for subsequent testing based on test results.

Have a question or comment? Add your thoughts to the Comments below. Click here to go to the next page .