Co-relation: is a process of capturing(extracting) dynamic data from the response of a request and passing it to next/subsequent requests.
Note: The process of co-relation is different in different tools.
Parameterization: is a process of passing static(known) data to a request(s). Generally, values to be passed/parameterized are saved in a file(.csv).
eg: Usernames and passwords...etc
What values need to be co-related and what values need to be parameterized?
It depends on
1. Dynamic/static data?
2. Volume of data need to be parameterized?
3. Complexity involved in co-relation
eg: Consider an eCommerce application with following transactions
1. Log in to the eCommerce application with Username and Password(Parameterization)
2. Select a random product out of l lac products(Co-relation)
3. Add to cart
Now, you want to load test above test case/test script with 1000 users
Step 1:
Log in to the eCommerce application with Username and Password
To do that you need 1000 usernames and corresponding passwords before starting a load test, in this case you have to put all usernames and passwords in a file(.csv) and pass to corresponding request. This is called Parameterization
Step 2:
Select a random product out of l lac products
To select a random product from l lac products, its not feasible to put all 1 lac products in a file and pass it to corresponding request, because it creates lot of overhead, instead write a co-relation rule to select a random product from available 1 lac products.
Additional Info
If an application is a .net based application then there will be page state variables such as View State, Event Validation, Event Target..etc these values will change for every page in this case you need to co-relate these values.
If an application has select box with 4 values(IT, CSC, ECE, Mech) and they constant for every user, then parameterization is feasible here instead of co-relation.
Note: What values need to be co-related and what values need parameterized are majorly depends on the application context, Co-relation will have more overhead on a load test when compared with Parameterization.
Parameterization: is a process of passing static(known) data to a request(s). Generally, values to be passed/parameterized are saved in a file(.csv).
eg: Usernames and passwords...etc
What values need to be co-related and what values need to be parameterized?
It depends on
1. Dynamic/static data?
2. Volume of data need to be parameterized?
3. Complexity involved in co-relation
eg: Consider an eCommerce application with following transactions
1. Log in to the eCommerce application with Username and Password(Parameterization)
2. Select a random product out of l lac products(Co-relation)
3. Add to cart
Now, you want to load test above test case/test script with 1000 users
Step 1:
Log in to the eCommerce application with Username and Password
To do that you need 1000 usernames and corresponding passwords before starting a load test, in this case you have to put all usernames and passwords in a file(.csv) and pass to corresponding request. This is called Parameterization
Step 2:
Select a random product out of l lac products
To select a random product from l lac products, its not feasible to put all 1 lac products in a file and pass it to corresponding request, because it creates lot of overhead, instead write a co-relation rule to select a random product from available 1 lac products.
Additional Info
If an application is a .net based application then there will be page state variables such as View State, Event Validation, Event Target..etc these values will change for every page in this case you need to co-relate these values.
If an application has select box with 4 values(IT, CSC, ECE, Mech) and they constant for every user, then parameterization is feasible here instead of co-relation.
Note: What values need to be co-related and what values need parameterized are majorly depends on the application context, Co-relation will have more overhead on a load test when compared with Parameterization.
No comments:
Post a Comment