Performance Testing – Scripting Checklist for Web Applications.

In this page, I will provide you the checklist for scripting a web based application.

It is the basic approach to that need to follow while designing scripts for web based applications.

1.   Connectivity to application

• It is important to check the connectivity of application from the environment / Network where scripting will be done. 
• If application is not accessible from network (where scripting will be done), then PT team need to highlight the same to application team so that application team can work on setting up the need (probably by white listing IP, etc.)

2.   Understanding Business Flow

• Prior to start scripting, we need to go through business flow and understand the scenario. 
• Be clear with the navigation and data required to compete end to end flow, it avoids confusion and helps to record the flow accurate.

   3.  Recording business flow 

• Clear cache, cookie and close all the opened windows of browser before start recording.
  
• While recording flow, add comments to each transaction.

4.   Post recording process

• Once recording is over, filter unnecessary or third party URLs from the script.
  
• Check if the all traffic of business flow is captured.

5.   Parameterization

• Ensure input parameters such as username, password or any other (as per script requirement) are done properly.
  
• It is also important that how these parameter are set. For example, unique, sequential etc.
• Place parameter settings as per script requirement.

6.   Correlation

• It is the process of handling dynamic string / values within the script. Ensure all the correlations are done properly.
  
• In order to identify the dynamic value, we may record the flow twice or can use chrome developer tools / Fiddler.
• While doing correlation, it is important to double check the fields such as scope (where to look for a match), match count (which occurrence to capture).

7.   Response Check Points

• It is essential to keep response check points in the script.
  
• This is because, performance testing tools only display error on basis of status code received.
• But, there are chances that even though response code is 200 OK, server still not responded with valid or expected (successful) response.
• To overcome this issue, response check points need to be inserted in the script. 
• While inserting check points, we need to use unique text (to check in response) in such a way that the text only appears in the response if the server responded as expected or correct.

8.   Write response to file

• Ensure input parameters such as username, password or any other (as per script requirement) are done properly.
  
• It is also important that how these parameter are set. For example, unique, sequential etc.
• Place parameter settings as per script requirement.

9.   Replay script

• Replay script once above mentioned tasks completed, validate if the script worked fine.

10.   Naming and creating Transactions

• Add proper / meaningful  naming convention to the transactions recorded. 
• Ensure to pass or fail a transaction based on the result of response check point.

It is also suggested to have a backup of the script and to maintain a version of script.