How does licensing work when executing an Eggplant Functional script in an Eggplant Performance Test?
Eggplant Performance Documentation states:
“Each Eggplant Functional VU uses an instance of Eggplant Functional (running in Drive mode) to communicate with the system under test (SUT). The Eggplant Performance injector automatically starts an instance of Eggplant Functional for each virtual user.
To run Eggplant Functional virtual users (VUs), your injector machine(s) must have Eggplant Functional installed and licensed using an appropriate Eggplant Functional (Drive-enabled) license.”
For more information please see the following link below:
Licensing Eggplant Functional for Use with Virtual Users
Eggplant Functional scripts executed within Eggplant Performance Test require specific licensing based on the use case. Virtual user scenarios necessitate both Eggplant Functional and Performance licenses, while non-virtual user scenarios require only an Eggplant Performance license. Refer to the official Eggplant documentation for detailed licensing information.
Hello,
When executing an Eggplant Functional script within an Eggplant Performance Test, the licensing requirements are as follows:
Eggplant Functional License: Each Virtual User (VU) running an Eggplant Functional script in an Eggplant Performance test requires a valid Eggplant Functional license. This license can be either:
Node-locked: Tied to a specific machine.
Floating: Available on a license server for flexible usage across multiple machines.
Eggplant Performance License: The Eggplant Performance Test Controller itself also requires a valid license, independent of the Eggplant Functional licenses used by the VUs.
Key Points:
License Consumption: Each VU utilizing an Eggplant Functional script will consume one Eggplant Functional license during test execution.
License Management: If using floating licenses, ensure the license server has enough available licenses to accommodate the number of concurrent VUs.
License Types: The type of Eggplant Functional license (node-locked or floating) will determine how you manage and allocate licenses for your performance testing environment.
In Summary:
To successfully execute Eggplant Functional scripts within an Eggplant Performance Test, you must have:
A valid Eggplant Performance Test Controller license.
A sufficient number of valid Eggplant Functional licenses for each VU that will be running an Eggplant Functional script.
By understanding these licensing requirements, you can ensure that your performance tests can run smoothly and efficiently.
Best Regards