Now that we've outline the testing process, it's important to focus on some of the key activities that you and your team should be performing throughout the various stages of this process.

Here are the most important activities for each part of the process:

Targets and requirements

1. All business requirements, discussed with sponsors and product owners
2. Business targets converted into a technical Service Level Agreement(s)
3. Discuss Service Level Agreements with the technical team (feasibility, and correctness)
4. Discuss performance test targets with technical & business stakeholder(s)
5. Set Service Level Agreements

Test environment

There are two parts in this phase of the performance testing process:

1. Part 1: Deploy the application on a separate performance testing environment. (Note: creating an exact replica of production environment is optimal while designing a performance test.)
2. Part 2: Performance test infrastructure: Procure performance testing software licenses(if required). Setup Software infrastructure based on business requirements. Make the software available for the entire testing team

Test strategy

This series of tests address business targets:

1. Conduct, and finalize, various work load models for each different type of tests
2. Recreate, and run tests from different geographic locations where potential clients may use the application

Scripting

1. Write, or record, any needed testing scripts and update them where appropriate
2. Add Thinktime and pacing time values
3. Add Text (and image) check points to the script
4. Define Co-relation points (for dynamic content)

Test data

1. Add production data to scripts, and make them more dynamic
2. Add appropriate date and time functions

Workflow model

1. Based on test design, create a workflow model using a scenario generator of different tools

Environment check

1. Create an environment test scenario based on the final production infrastructure your application operates in (or will operate in)
2. Manually execute the test environment before the performance test
3. Clear any logs created in the environment before the test runs

Test execution

1. Execute the test
2. Monitor the application, database and web servers while the test executes

Results analysis

1. Collate, and study client side counters
2. Copy test results from analysis tools and compare with previous tests
3. Note, and document, all necessary improvements to made in the application
4. Identify all application issues, and show reports to performance engineering team

Results Report

1. Add all key items from the last phase into the report
2. Add key client side counters to report
3. Add error details to the report, along with necessary observations.