Prioritizing Correlation Rules in a COR file

Our Articles

Prioritizing Correlation Rules in a COR file
Apr 25th, 2020 7:04 pm    Anand Govindasamy - JMX Enhancer

Ever since the dawn of Performance Testing, we have been trying to minimize the time taken to enhance performance test scripts. Many tools in the market have implemented Correlation/Framework rules to accomplish this. However, they are missing a simple but important feature i.e. Prioritizing the correlation rules.

We believe that a parameter which appears within another parameter (i.e. kind of a sub parameter) should be prioritized later during auto-correlation.

Let us discuss this with a real-world scenario. Consider that we have the below 2 parameters that needs to be correlated.

                            Parameter-1 Name : DocIdentifier
                            Parameter-1 Value : APX258G5TM65
                            Regular Expression : DocId:“(.*?)”

                            Parameter-2 Name : AttachmentInfo
                            Parameter-2 Value : LINK-ATTACHMENT KG5–90TC APX258G5TM65 !
                            Regular Expression : AttachmentInfo(.*?)&

If DocIdentifier get correlated first, Parameter-2’s value gets updated as “LINK-ATTACHMENT KG5–90TC ${DocIdentifier} !” after the auto-correlation process. Now the Dynamic Parameters Identification Engine moves on to correlate Parameter-2. It is not able to find the value “LINK-ATTACHMENT KG5–90TC APX258G5TM65 !” since it has already been updated. In such a situation, we will have to cleanup the entire script and it becomes a tedious work if the script is large.

Correlating Parameter-1 after Parameter-2 will solve this issue. Hence we recommend users to prioritize their correlation rules in the COR file that is fed to the JCorrelate tool. The COR file needs to have the correlation rules in the same sequence as they need to be executed.


Note : Prioritizing the correlation rules is just optional and is not mandatory. We are helping you to utilize the best capabilities in our solutions.

Previous Article Blog Home Next Article