Use framework parameters to automatically search for dynamic parameters

This tutorial will show you how to automate dynamic parameter handling using framework parameters.

To get the most out of this tutorial, it is recommended to read the following tutorials beforehand:

• Create a variable extractor<in_pdf_tuto>.
• Handle an application dynamic parameters<in_pdf_tuto>, in order to understand the steps involved in defining a variable extractor.

In This Section Understand the problem Example How framework parameters work Create a framework parameter Access framework parameters Changes implemented in the scenario

See Also Design - Dynamic Parameters Choose a data extraction method Handle an application dynamic parameters Create a variable extractor Submit a form from the previous request Follow a link from the previous request

Understand the problem

The HTML pages generated by applications usually contain dynamic elements, that is to say components whose values vary from one call to the next. Typically, these include unique identifiers that cannot be replayed "as is", and which must be managed individually.

When dynamic parameter handling fails:

• requests may show an error (typically, Error 500) when checking the Virtual User validity;
• the Virtual User displays an unexpected behavior (entries not created in the database for example).

NeoLoad automatically handles the most common parameters, such as the Framework .Net __VIEWSTATE parameter. However, NeoLoad cannot automatically handle parameters specific to an application. They need to be handled individually, that is to say by placing an extractor on the value returned by the server and injecting the extracted value into the appropriate requests.

NeoLoad provides the necessary tools to handle a dynamic parameter manually. See Handle an application dynamic parameters<in_pdf_tuto>.

Home