Forum Discussion

RVS's avatar
RVS
New Contributor
9 years ago

Parameter values not taken into account during test runs

I am experiencing some issues when running test with custom parameter values.

In particular, the custom parameter values are ignored in the test runs and the parameter value is set to the one utilised to record the scenario.

 

The procedure I utilised for the set up follows the tutorial that can be found at https://support.smartbear.com/viewarticle/78497/

The only difference is for the data source of the variables, for which I utilised the "LoadComplete variable" instead of the Excel one mentioned in the tutorial.


Following a step-by-step description of the procedure I utilized.

 

1) Select the scenario of which I want to set the parameters.

 

2) Click on the "Set Parameter Values..." button.

 

Note: After clicking on the "Set Parameter Values..." button, the browser utilised for running the test automatically opens. I am not sure if this is a desired behaviour of the application and, in case, why the browser is launched.

 

3) Select the variable for which I want to utilise different custom values (In my case ctl00%24MainContent%24Username)

 

 

 

4) After setting the new variable name I select the "LoadComplete Variable" option and afterwards the "List Variable" option.

 

5) To make sure that the value utilised for the recording is not used, I remove it and add two different values (namely "foo" and "bar")

6) Select the "Item index equals virtual user index" option and then "finish". The application returns to the overview of the variables. 

 

 

7) I double-check that the parameter is correctly set in the request body and it seems OK.

 

 

8) I set the number of virtual users of the Scenario Test to two. Theoretically one of the virtual users should use the "foo"value and the other one the "bar" value in the above mentioned field.

9) I run the test of the Scenario and control the inputted parameter for both virtual users, the variable is still set to "test1"

 

Does anyone know how to solve this issue?

  • RVS's avatar
    RVS
    New Contributor

    I found a possible workaround for the issue: By redefining again the value of the variable to the one that was already set (i.e. in my case the @username list) in the request body after Step 7 the correct values are taken. 

     

    Note: The same issue was encountered while using a .CVS file as data source.

    • AlexeyKryuchkov's avatar
      AlexeyKryuchkov
      SmartBear Alumni (Retired)

      Hi,

       

      According to the description, it looks like you've faced a known LoadComplete 4 issue. So, if you are using LoadComplete 4.0 or LoadComplete 4.10, please try upgrading to LoadComplete 4.20 - the issue is fixed there.

      • RVS's avatar
        RVS
        New Contributor

        I can indeed confirm that I utilised the release 4.10.1780 to set up the parameter values.

        Kr,

        RVS