DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The Request Timed Out, But the Payment Succeeded: Building Retry-Safe Mobile APIs
  • How to Prevent Retry Storms With Retry Budgets in Distributed Systems
  • A Developer's Guide to Chrome Extension Manifest V3 Declarative Net Request API
  • From Microservices to Agent Services: The Next Architectural Shift

Trending

  • The Warning That Never Stops the Agent
  • Building an AI-Ready Data Layer Without Rebuilding the Enterprise
  • Why Databricks and Snowflake Speak the Kafka Protocol: Ingestion vs Architecture
  • Stop Paying a Model to Make Decisions You Already Made

Handling Variable Number of Request Parameters in Neoload

This brief tutorial will show you how to handle multiple request parameters using Neoload and JavaScript for efficiency.

By 
Manojkumar Tenali user avatar
Manojkumar Tenali
·
Updated May. 30, 18 · Tutorial
Likes (3)
Comment
Save
Tweet
Share
12.4K Views

Join the DZone community and get the full member experience.

Join For Free

If your request has a lot of parameters which are being passed to HTTP Request, creating a request to manually correlate the data will be a cumbersome process when instead, we can use scripting capabilities using JavaScript in Neoload to make a much easier and effective way of handling them.

Image title

Steps to Handle "Too Many Request Parameters" With Dynamic Values

  1. Correlate the request parameters using variable extractors.
  2. Using Javascript, construct the string with all the request parameters and store that in a variable.
  3. Change the Post Content Type to Text in HTTP Request.
  4. Pass the variable into the request.

Here is a practical explanation.

Capture the variables using variable extractors from the preceding request as below.

Image title

Click on edit and create the Regular expression as below and select Extract All Occurrences.

Image title

You would be able to see the extracted value under the test header as above.

Now drag and drop Javascript action on to the userpath as below and enter the following JavaScript Code:

Image title


var countinstring = context.variableManager.getValue("KeyString_matchNr"); // getting count of captured values and storing into the string
var countinint = parseInt(countinstring); // converting count to integer value

var string = "";

for (var i = 1; i <= countinint; i++) {
    var key = context.variableManager.getValue("KeyString_" + i); // getting each key variables
    var value = context.variableManager.getValue("ValueString_" + i); // getting each value variables

    string = string + key + "=" + value + "&"; // concatenating each key and value pairs

}
logger.debug("concatenated string=" + string);
string = string.substring(0, string.length - 1); //remove extra & 

// Inject the computed value in a runtime variable
context.variableManager.setValue("variableString", string); // storing the constructed concatenated string to a variable


Please refer to JavaScript API of Neoload community.

The final step is to change the Post Content type to Text as below and pass the captured value as a parameter.

POST requests with a text/... -type content. The contents of these requests may contain NeoLoad variables for generating dynamic content.

Image title

Now click on check user path and click on start checking to validate the scripts to check the variables being captured currently or not as below

Image title

Source.

This way we can handle any number of dynamic parameters.

Requests

Opinions expressed by DZone contributors are their own.

Related

  • The Request Timed Out, But the Payment Succeeded: Building Retry-Safe Mobile APIs
  • How to Prevent Retry Storms With Retry Budgets in Distributed Systems
  • A Developer's Guide to Chrome Extension Manifest V3 Declarative Net Request API
  • From Microservices to Agent Services: The Next Architectural Shift

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook