Performance test plan are backbone of performance testing and they set the path to drive through whole testing process, It should clear all doubt roaring our mind about performance test like what to test, how to test, what is the criteria. A good test plan drives the project to achieve it's goals without any major difficulties.
While working in IT industry and for different vendors you may see changes in the test plan and every company maintain their our Test plan.
As mentioned test plans changes with the companies but their structure and basic need and fields remains same everywhere,It will portray answer for each question for our testing purpose.
A test plan should posses:
1. Document Information/Objective of the test
This section provided the high level summary of the need for this performance testing, It provided summary about test plan as well what all sections will be covered within the test plan
There are two basic parts for this section
This section contains following below information
While working in IT industry and for different vendors you may see changes in the test plan and every company maintain their our Test plan.
As mentioned test plans changes with the companies but their structure and basic need and fields remains same everywhere,It will portray answer for each question for our testing purpose.
A test plan should posses:
1. Document Information/Objective of the test
This section provided the high level summary of the need for this performance testing, It provided summary about test plan as well what all sections will be covered within the test plan
There are two basic parts for this section
- About the document
- Document Approval/Sign off
This section contains following below information
- Application Name
- Application Description
- Application Platform/Run-Time environment
- Application flow
- Application/System technology employed
3. Key Business function definition
This section will provide information about what all business functions are in scope and need to be tested.
4. Performance test workload model
User / Business Transaction based workload will be given under this section
5. Test Scenario
Contains what type of test scenario will be performed as part
of this testing effort. e.g. Average, Peak Hour, Soak etc.
This section also contains the information about ramp-up, ramp-down, think time as well.
6. Test User Profiles and IDs
This section the various types of user profiles that will be needed to test the application are defined, Laso the roles and entitlements of the test IDs will be described
7. Test Data
Test data id the base for any performance test, It could be nay form like URL, User IDs/Password and application specific data, this section described all types of data going to be used and where we can get the data from, Data is also provided by the data team and it should be mentioned how to take data ot the methods to process the data.
8. Test tools
Tools which will be used in testing will be descibed here with their versions
9. Test Schedule
Time line given to complete the testing will be described in this section, though its hard to calculate time lines but tentative periods should be defined in this section.
10. Issue tracking process
How the issues and bottlenecks found in the testing will be tracked and what tool or methodology will be used to track them.
6. Test User Profiles and IDs
This section the various types of user profiles that will be needed to test the application are defined, Laso the roles and entitlements of the test IDs will be described
7. Test Data
Test data id the base for any performance test, It could be nay form like URL, User IDs/Password and application specific data, this section described all types of data going to be used and where we can get the data from, Data is also provided by the data team and it should be mentioned how to take data ot the methods to process the data.
8. Test tools
Tools which will be used in testing will be descibed here with their versions
9. Test Schedule
Time line given to complete the testing will be described in this section, though its hard to calculate time lines but tentative periods should be defined in this section.
10. Issue tracking process
How the issues and bottlenecks found in the testing will be tracked and what tool or methodology will be used to track them.
No comments:
Post a Comment