These pages provide the background and information for working with eggplant Performance, TestPlant's load and performance testing tool.

Transcription

1 Published on Documentation ( Home > eggplant Performance eggplant Performance eggplant Performance These pages provide the background and information for working with eggplant Performance, TestPlant's load and performance testing tool. Table of Contents eggplant Performance User Guide [1] (Note: This is under the Help menu in eggplant Performance Studio) Welcome to eggplant Performance [1] Getting Started with eggplant Performance and Studio [2] Virtual Users [3] Parameterization [4] Shared Data Server [5] Monitoring [6] Getting Started with eggplant Performance Test Controller [7] Getting Started with eggplant Performance Analyzer [8] Advanced [9] Troubleshooting [10] API Reference Manual [11] Virtual User API Reference Guide (Java) [12] Overview Package Class Use Tree Deprecated Index Help Virtual User API Reference Guide (C++) [13] C++ API for TCP and UDP Protocols Classes Files Virtual User API Reference Guide (C#) [14] New Features in eggplant Performance v6.2.0 Below is a list of new features in version 6.2.0: Comprehensive support for SOAP Web Services as follows: Generate code for testing a web service from a WSDL. Generated code can be C# or Java. SOAP 1.1 and 1.2 are both supported. Easily generate scripts that target the web service. All serialization/deserialization of XML is handled behind the scenes. Thus, scripts are clean and simple, with no complicated correlations or transformations necessary. Improved recording of mobile applications using the Proxy Recorder: The Trusted Root Certificate generated by the Proxy Recorder is now accepted by ios and Android devices, allowing HTTPS traffic from apps to be recorded. 1

2 Improved UI guides you through the process of setting up recording of HTTP(S) traffic to/from your mobile device. Better support for handling timestamps in web recordings: Automatically identify timestamps and generate a timestamp to replace them with. Replacements can be either the current time, a fixed time, or a time generated by custom code. Data correlation generation rules now allow you to specify a regular expression to use during extraction. Support for Microsoft Visual Studio 2015 and.net 4.6. Improved management of.net assemblies. Improved image scalling in the eggplant Functional Viewer window. Improved event log filtering in Test Controller. Automatic check for new releases of Studio and Analyzer. New overloads for the ExtractList() method. New GetValue() method added to the Url class. Project exports now have the extension.epa (eggplant Performance Archive), rather than.zip. (But both.zip and.epa formats are supported for imports). You can exclude specific extensions from a project archive. (For example, you could exclude video content in order to reduce the size of the export.) New Features in eggplant Performance v6.1.0 Below is a list of new features in version 6.1.0, followed by a video demonstration: Completely new Analyzer component Powerful new chart creation Ability to filter/split data by injector/script/group Improved reporting, including PDF reports New comparison charts allow the user to compare multiple test runs and easily identify trends Key Performance Indicators can be defined and reported on REST API allows full automation of the analysis and reporting process Uses a postgres database to store the analyzed data eggplant Performance Overview 2

3 Using eggplant Functional VUs Help and Additional Information Manuals You can access all of the following manuals online through the TestPlant Documentation website [15]. You can also access documentation within individual products by going to Help > Documentation. Getting Started [16] provides instructions for a basic eggplant Functional set up to get you started using this testing tool and familiarize you with its functionality. Using eggplant Functional [17] is a collection of articles that delve into the eggplant Functional workflow and explain a variety of important tasks and concepts such as how to organize your testing process and how to use eggdrive to integrate scripts from other testing tools. eggplant Functional Reference [18] describes the eggplant Functional interface and scripting processes, and the SenseTalk commands, functions, and global properties that are unique to eggplant Functional. SenseTalk Reference [19] is a comprehensive guide to the SenseTalk scripting language used with eggplant Functional. This manual discusses all aspects of the SenseTalk language that are used for general scripting purposes. Commands and functions that are unique to eggplant Functional are also described here. The eggplant Performance [20] manual describes how to set up, run tests, and view results with eggplant Performance, a load and performance testing tool. The eggplant Manager [21] manual provides instructions for a basic set up of eggplant Manager, a test management system. Learn how to schedule and execute tests and view results. The eggcloud [22] manual describes how to deploy and administer eggcloud, a test-reservation system. You'll also 3

4 learn how to make reservations and how to connect through eggcloud. The eggman [23] reference helps you set up and get started using this free tool for manual testing. The eggbox [24] manual describes this appliance, which comes with a range of pre-installed TestPlant tools and related applications, and shows how you can use it to easily set up and run a test lab. The eggplant Network [25] reference describes the eggplant Network appliance and how to use it to emulate network conditions when testing with eggplant Functional and eggplant Performance. Connecting to SUTs [26] is a reference for everything you need to know about how to connect to and test against mobile devices with eggplant Functional using either eggon or ios Gateway. The Knowledge Base [27] is a collection of articles from different contributors that describe a variety of techniques and approaches to using eggplant Functional, as well as best practices and use-case scenarios. Further Resources The Examples section [28] of the TestPlant documentation provides a variety of example scripts using SenseTalk to run eggplant Functional tests, which you can adapt to fit your testing needs. The FAQ section [29] gathers common problems and solutions for TestPlant products. Online eggplant Functional Tutorials: [30] This series of four interactive tutorials introduces the scripting environment and some frequently used commands and functions. eggplant Functional User Forum: [31] Use this forum to ask questions of other eggplant Functional users, help your peers, and share ideas and approaches for using the product. eggplant Functional Examples Forum: [32] This forum is a collection of eggplant Functional scripts written in SenseTalk that address a variety of scripting problems. About eggplant Performance About eggplant Performance What is eggplant Performance? eggplant Performance is a set of tools for load and performance testing of application clients, servers, networks, and network devices. By measuring performance at these different layers of a system under test (SUT), eggplant Performance provides a uniquely comprehensive analysis of both the user experience of an application and the capabilities of the supporting hardware, software, and network. eggplant Performance testing is achieved by simulating the actions of real users and replacing them with efficient, lowoverhead, and consistent Virtual Users. As such, Virtual Users represent a method for quickly, simply, and repeatedly assessing the performance of a SUT, resulting in shortened product cycles and an improved user experience of an application. eggplant Performance includes a number of powerful and easy-to-use tools that facilitate the creation of dynamic Virtual Users. These tools allow one to create complex, advanced tests where each Virtual User has its own unique data and timings. Additionally, groups of Virtual Users can run different scripts or workflows within the same test, simulating a variety of user stories. By acting as an engine for coordinating the execution of dynamic and variable Virtual Users, eggplant Performance simplifies the process of deploying realistic performance tests against a SUT and its environment. Which Technologies Can eggplant Performance Test? eggplant Performance supports numerous protocols, communication interfaces, data formats and programming languages, enabling performance testing of many types of servers and distributed applications, including: Web servers, databases, EJB servers, Microsoft.Net services, SOAP, Citrix servers, mail servers, telnet services, mainframe systems, proprietary applications, or load testing by automating the user interface. eggplant Performance uses an open and extensible framework that can provide the solution to numerous load and performance testing requirements. Support for new protocols or interfaces can be added quickly by the user. Tools including recording capabilities and support for common, powerful, and accessible scripting languages make performance testing with eggplant Performance straightforward and easy to adopt. eggplant Performance can act both as a server and a client, allowing eggplant Performance to generate load for the testing of network infrastructures, intermediate layers of N-tier architectures, as well as equipment such as routers and content-aware network devices. What Does an eggplant Performance Testing Environment Look Like? 4

5 The applications comprising the eggplant Performance set of tools are eggplant Performance Studio, Test Controller, and Analyzer. The eggplant Performance testing environment consists of a controller machine, where tests are designed and initialized; injector machines, where tests are executed; and the system(s) under test, which can include back-end databases and webservers, or instances of a front-end client. In cases where a limited number of Virtual Users are required, the controller machine and injector machine can consist of a single physical machine. The addition of injectors allows the straightforward scalability of tests. Set-up and Installation Set-up and Installation of eggplant Performance This section describes the installation and initial set-up of the eggplant Performance set of applications and includes information on system requirements and prerequisites and product licensing. For all information about installation and licensing of eggplant Performance, please see the eggplant Performance Release Notes [33]. Prerequisites for Installation Prerequisites for Installation eggplant Performance: Studio, Test Controller, and Analyzer This section provides information on Hardware requirements, supported operating systems, and other requirements for running the eggplant Performance Studio, Test Controller, and Analyzer version Supported Operating Systems 5

6 eggplant Performance Studio and Test Controller run on Windows only. Below is a list of supported Windows operating systems. eggplant Performance Analyzer only runs on the 64-bit versions of the following Windows operating systems. Windows Vista (32-bit and 64-bit) Windows Vista SP1 (32-bit and 64-bit) Windows 7 SP1 (32-bit and 64-bit) Windows 7 SP1 (32-bit and 64-bit) Windows 8.1 (32-bit and 64-bit-all versions except RT) Windows Server 2008 (32-bit and 64-bit) Windows Server 2011 (32-bit and 64-bit) Windows Server 2012 (32-bit and 64-bit) Windows Server 8 (32-bit and 64-bit) Windows Server 10 (32-bit and 64-bit) Note: Support for Windows XP and Windows Server 2003 has been dropped in v5.4.0 Hardware Recommended minimum 2GHz processor, 2Gb RAM, 200Mb free for the installation. You will also need additional disk space for the test run results data. Microsoft.NET 4.5 To run Studio, Test Controller, Analyzer or the C# engine, Microsoft.NET 4.5 must be installed. You can download it here [34]. Additionally, Microsoft.NET Framework 4 Client Profile and Microsoft.NET Framework 4 Extended must both be installed (available via Microsoft Update, and also from here [35]). Script Builders Virtual User scripts are available in a number of languages dependent upon the VU type. For C++ and C# Virtual Users Any one of the following are suitable (latest version preferred): Microsoft Visual Studio.NET 2008 Microsoft Visual Express Edition 2008 (freely available from Microsoft) Microsoft Visual Studio.NET 2010 Microsoft Visual Express Edition 2010 (freely available from Microsoft, but must be registered) Microsoft Visual Studio.NET 2012 Microsoft Visual Express Edition 2012 (freely available from Microsoft, but must be registered) Microsoft Visual Studio.NET 2013 Microsoft Visual Express Edition 2013 (freely available from Microsoft, but must be registered) For Java Virtual Users 32-bit Java JDK 1.5 or later. Note: We supply a Java 1.7 JDK with Studio, and we also supply a new Eclipse plugin for integration with Eclipse. eggplant Performance Injectors The eggplant Performance Injectors run on Windows, Mac and Linux operating systems as described below: Supported Operating Systems Windows Windows Vista SP1 (32-bit and 64-bit) Windows 7 SP1 (32-bit and 64-bit) Windows 8.1 (32-bit and 64-bit; All versions except RT) Windows Server 2008 (32-bit and 64-bit) Windows Server 2011 (32-bit and 64-bit) Windows Server 2012 (32-bit and 64-bit) 6

7 Windows Server 8 (32-bit and 64-bit) Windows Server 10 Note:Support for Windows XP and Windows Server 2003 ended in a previous release. Mac Linux OS X OS X 10.9 All versions of Linux are supported. Hardware The system requirements needed to support a load test are dependent upon a number of factors. The specifications listed below will comfortably support up to 1000 Web Virtual Users. Recommended minimum 2GHz processor, 4Gb RAM, 100Mb free for the installation. You will also need additional disk space for the test run results data. Microsoft.NET 4.5 To run the C# engine, Microsoft.NET 4.5 redistributable must be installed. This is installed automatically when the injector is installed. Additionally, Microsoft.NET Framework 4 Client Profile and Extended Profile must be installed (available via Microsoft Update, and also from here [35].) Java Runtime The Java Runtime on the injector should be compatible with the runtime on the Controller. It is recommended that you use the packaged version. The Java Runtime must be 32-bit as 64-bit JREs are not supported. Installing the eggplant Performance Controller Installing the eggplant Performance Controller This page covers installation of the eggplant Performance Controller software [36] itself, and information about transferring the eggplant Performance Controller [37]. Step-by-Step: Installing the eggplant Performance Controller 1. Download [38] the latest eggplant Performance installer (includes Studio, Test Controller, and Injector components) from the TestPlant website. 2. Run the installer program which will install a local (localhost) Injector alongside the Studio and Test Controller executables. 3. Only one instance at a time of eggplant Performance controller can run on a machine. 4. Depending on your needs, you might need to further license eggplant Performance Studio in order to use it. 5. eggplant Performance is regularly updated so please periodically check the Downloads page of our website to check for new releases and for details of new features. Step-by-Step: Transferring the eggplant Performance Controller If you wish to subsequently move your installation and license to another machine, please complete the following steps: 1. Export your Workspaces and Projects in preparation for the move. 2. Install the prerequisites on the target machine. 3. Transfer [39] your license from the old machine to the target machine. 7

8 4. License the target machine. Setting Up Injectors Setting Up Injectors Injectors are the machines that execute your test. The localhost can act as an injector for tests with limited numbers of Virtual Users (VUs), but often additional injectors are needed. Setting up additional injectors lets you simply and quickly scale your test. Additional injectors facilitate higher numbers of VUs, which generate greater load and concurrency. Hardware Requirements The machine resources required for an eggplant Performance load injector is dependent on the VU types, test scripts, and other variables. As a (very) rough guide, to support up to 1000 web VUs, the recommended system resource minimums are a 2 GHz multi-core processor, 4GB RAM, and 100MB free disc space for the installation. You also need additional disk space for the test run results data. This data can range from a few kilobytes to many gigabytes depending on the test run options selected, the level of logging, the duration of your test runs, and the number of simulated VUs. Virtual User Support Microsoft Windows, Linux, and Mac OS X machines can all be used to run as injectors but are restricted as to which types of VUs they can execute. Supported VUs Windows OS X Linux All Java (excl. Java Web), epf, Selenium Java (excl. Java Web), epf, Selenium JRE Included in installation Not included in installation Required; installed by user.net Platform Required; installed by user N/A Web Java and.net based Virtual Users (Web C#, Citrix, and WinDriver) These Virtual Users can run only on Microsoft Windows platforms, and the full.net Framework 4.5 must be present. Java (non-web) Virtual Users On Windows or Linux injectors, no additional prerequisites are needed, as 32-bit Java JRE version 1.7 is installed with the product. The Java platform must be installed separately for OS X machines. A different Java JDK/JRE may be selected after eggplant Performance has been installed. Note: 64-bit Java is not supported for Java Web Virtual User execution but can be used for other Java Virtual User types. N/A Platform-Specific Installation The steps for setting up an injector vary by platform. Check the appropriate article below for your operating system. Linux: Setting Up an eggplant Performance Injector Linux: Setting Up an eggplant Performance Injector 8

9 Follow these setup instructions to configure additional injector machines on Linux systems when the eggplant Performance Controller's localhost injector is not sufficient for testing. Step-by-Step: Set Up an Injector on Linux 1. Download [38] the latest eggplant Performance Injector (Linux) installer from the TestPlant website. Note: The Linux injector is distributed as a.zip file. 2. Unzip the downloaded.zip file. 3. Run install.sh inside the unzipped directory.../install.sh 4. Run runinjector.sh inside the bin folder in the unzipped directory.../runinjector.sh Note: You do not need to be running as the root user in order to run the injector. 5. Configure the port on which the injector listens for connections from the Test Controller machine by passing the desired port as a parameter to runinjector.sh.../runinjector.sh Mac: Setting Up an eggplant Performance Injector 9

10 Mac: Setting Up an eggplant Performance Injector Follow these setup instructions to configure additional injector machines on Mac systems when the eggplant Performance Controller's localhost injector is not sufficient for testing. Step-by-Step: Set Up an Injector on Mac 1. Download [38] the latest eggplant Performance Injector (OS X) from the TestPlant website. Note: The Mac OS X injector is available to download as an application package.pkg file. 2. Ensure a recent Java Development Kit (JDK) and not just a Java Runtime Environment (JRE) is installed before installing the injector. Note: From the Oracle Mac OS FAQ [40]: "Installing a JRE from Oracle does not update java -version symlinks or add java to your path. For this functionality, you must install the full JDK." a. To determine whether a JDK is installed, run the following command in a Terminal window: java -version b. If necessary, install the JDK. 10

11 11

12 3. Click the Mac OS X injector.pkg to launch Apple's installer application. 4. Enter your Mac user account username and password if requested during the installation. 12

13 13

14 Note: The Mac OS X injector runs as a daemon, which starts as soon as the installation process is finished, and runs automatically whenever the Mac boots up. You should be able to connect to it from eggplant Performance Studio. You must have superuser permissions in order to start the daemon. Otherwise, the daemon starts with insufficient permissions to write to the log files. It responds to commands from eggplant Performance Studio, but will not work correctly. Viewing Injector Logs 1. Open the Console application in Mac OS X, which can be found under Applications > Utilities. 2. In the list on the left, click to expand /var/log. 3. Click eggplantperformanceinjectorout.log or eggplantperformanceinjectorerr.log. 14

15 Stopping the Injector Daemon 1. Run the following command in Terminal: sudo launchctl unload /Library/LaunchDaemons/com.testplant.injector.Injector.plist 2. Check for a message in the system log that says that the injector has exited. Note: If you do not have superuser permissions, you will see the following error when executing the command above: launchctl: Error unloading: com.testplant.injector.injector 15

16 Configuring the Injector Port By default, the injector listens for connections from the Test Controller machine over port However, this port can be configured with the following steps: 1. Stop the Injector daemon. 2. While operating with superuser permissions, open the.plist file located at /Library/LaunchDaemons/com.testplant.injector.Injector.plist 3. See below for the appropriate value to edit: 16

17 4. Restart the Injector machine to restart the daemon, or start the daemon manually by using the following command in Terminal: sudo launchctl load /Library/LaunchDaemons/com.testplant.injector.Injector.plist Windows: Setting Up an eggplant Performance Injector Windows: Setting Up an eggplant Performance Injector Follow these setup instructions to configure additional injector machines when the eggplant Performance Controller's localhost injector is not sufficient for testing. When upgrading a Controller, it is not usually necessary to upgrade the injectors unless explicitly required in the release notes. Note: An injector should not be installed on the same machine as eggplant Performance Studio because injector capabilities are already included with the Controller installation package. Step-by-Step: Set Up an Injector on Windows 1. Download [38] the latest eggplant Performance Injector (Windows) installer from the TestPlant website. 2. Execute the installer. Note: The injector components are available in a.zip file that might be extracted without running an installer. 3. Start the injector by running the batch file located (by default) in C:\Program Files (x86)\eggplant Performance\bin\. runinjector.bat 4. The injector will listen on port by default. To use a different port, pass the desired port number as a parameter to the batch file on the command line. runinjector.bat

18 Note: You will also need to set the corresponding injector port within the injector definition on the Controller. Installing the Injector Service It is often more convenient to install the injector as a Windows service. This configuration lets you manage the injector process remotely (if you have sufficient permissions). You can also set the injector to Automatic so that it restarts after a reboot has been performed. To install the injector as a service, run installinjectorservice.bat as an Administrator. This file is located in C:\Program Files (x86)\eggplant Performance\bin\ if you've done a standard installation of eggplant Performance. To change the Startup type from Manual to Automatic, follow these steps: 1. In the Windows Control Panel, open Administrative Tools, and then open Services. 2. Locate the service named "eggplant Performance Injector Service," right-click it, and then select Properties. 3. On the General tab, select Automatic from the drop-down list for Startup type. Note: If necessary, change the setting on the Log On tab from Local System account to an account with greater privileges; the Local System account often does not have the necessary permissions. 4. Click OK to apply your changes. Change the Default Injector Service Port By default, injectors will use port However, the injector can be set to use a different port by adding a line of code to installinjectorservice.bat before you run it. In the "Startup configuration" section of the.bat file, add the following line of code: 18

19 set PR_STARTPARAMS=-p;39001 With this code, the port would be changed from the default to To choose a different port, change the number in the above line of code. The "Startup configuration" section should look like this: REM Startup configuration set PR_STARTUP=auto set PR_STARTMODE=jvm set PR_STARTCLASS=com.testplant.injector.Injector set PR_STARTMETHOD=startWindowsService set PR_STARTPARAMS=-p;39001 If you've previously installed an injector on the same machine, make sure to uninstall the service before installing the modified.bat file. When launching the.bat file for installation, remember to use the Run as administrator option. Uninstalling the Injector Service 1. To uninstall the injector service, run the following batch file as Administrator, located in C:\Program Files (x86)\eggplant Performance\bin\ uninstallinjectorservice.bat Configuring Studio Preferences eggplant Performance Studio Preferences The Preferences dialog is used to access eggplant Performance Studio's user-configurable settings and is launched by selecting Tools > Preferences from the main menu. Use the Apply button to save changes immediately. Clicking OK will save any outstanding preference changes and exit the Preferences dialog. Clicking Cancel without first clicking Apply will result in changes not being saved. Cancel exits the Preferences dialog. General 19

20 Text Editor eggplant Performance is installed with a text editor for editing scripts in isolation from a configured IDE. The text editor is also used for editing data source files. The installed text editor is a freeware tool called SciTE that automatically applies syntax styling based on the type of text being edited. It can also hold multiple files in memory at one time to allow easy switching between different documents. To change the text editor to one of your own preference, use the associated browse button to locate an editor executable on your eggplant Performance Controller machine. Ant Ant is used for building Java project files. This setting defaults to the location of the Ant installation distributed with eggplant Performance. Use the associated browse button to locate Ant. JRE (Java Runtime Environment) The location of the Java Runtime Environment. This acts as the default JRE location for Java tests run on localhost. It is also used by the TCP/IP script generator when creating TCP scripts. Use the associated browse button to locate the JRE. eggplant eggplant Performance integrates with eggplant Functional, allowing the execution of eggplant Functional Virtual Users from eggplant Performance. This is the installation directory of eggplant Functional. Locations Save exports to: Use the browse button to select a default location for all exports. When you select the option to export an item, it will still be possible to override this value. Builders 20

21 It is possible to build Virtual User scripts targeted at multiple runtime engines. For example, native C++ Virtual Users can be compiled to run against runtime engines built with various versions of Visual Studio. However, during test execution only one runtime profile can be selected (see runtime profiles). In the table of builders check the box for each runtime against which you wish to build your Virtual User scripts. Each of the builders that you select must be available i.e. installed. Runtime Profiles eggplant Performance has multiple runtime engines for running different Virtual User types. For example, Web Virtual 21

22 Users are required to run within a native C++ runtime engine. Because of its inherent flexibility, eggplant Performance can utilize runtime engines built within various builder environments. A native C++ runtime can be built using Visual Studio. C++: Displays the selected runtime profile for C++ Virtual User scripts. Java: Displays the selected runtime profile for Java Virtual User scripts..net: Displays the selected runtime profile for.net Virtual User scripts. Workspace Use the browse button to select a default location for creating new workspaces. When you select to the option to create a new workspace, it is still possible to override this value. The eggplant Performance Workflow The eggplant Performance Workflow This section will guide you through creating and configuring a test with eggplant Performance Studio, executing and tracking the progress of the test in Test Controller, and analyzing and reviewing the results in Analyzer. The example test discussed in this section uses web Virtual Users based on a recording of http web traffic. Creating an eggplant Performance Test Creating an eggplant Performance Test This article provides a step-by-step example for creating an eggplant Performance test. Below, you can view a brief video that demonstrates eggplant Performance test creation leveraging web virtual users (VUs): 22

23 The test creation method presented below is one of a number of ways you can create a test in eggplant Performance. This example test focuses on the functionality of eggplant Performance Studio and how it can be used to manage VUs and tests. It leverages web VUs based on a recording of HTTP web traffic. 1. Create a Workspace Before you can create an eggplant Performance test, you must either open an existing Workspace or add a new one. The Workspace contains all environment-specific data such as injector details, default editors, compiler locations, and Custom Virtual User types. A Workspace allows you to switch between different environments easily, for example switching between a test and a LIVE environment, both of which will likely have different injector configurations. To create a new Workspace: a. Select File > New > Workspace. b. The Add Workspace dialog is displayed. Enter a name for the new Workspace in the "Name" field. 23

24 c. Enter a location for the desired physical location of the new Workspace in the "Location" field. d. Click "OK". 2. Create a Virtual User Before you will be able to generate scripts for use in your test, you must have a Virtual User available. Creating a new Virtual User type is done in preparation for script creation, but it is not necessary to do before creating each new script. For the purposes of these instructions, you will add a new Web Virtual User type, which supports the record and replay of user interactions with Web based applications and servers using HTTP and HTTPS. You create either a Java Web or C# Web Virtual User, depending on your preference. To create a new Virtual User: a. In the Workspace, right-click the "Virtual Users" heading and select "New Virtual User". b. Select "Web Java" or "Web C#" from the list and click "Next". c. Provide a Name for the new Virtual User. The Class name will automatically populate. 24

25 Click "Finish". 3. Create a Project eggplant Performance is a project based load testing tool. Scripts, workflows, data and tests are all held within a named project. You must either open an existing project, or create a new one. To create a new Project: a. Select File > New > Project or click the New Project button on the toolbar. The New Project dialog is displayed. b. Enter a name for the new Project in the "Project Name" field. c. Click "OK". Note: To save a Project select File >> Save or click the Save button on the toolbar. 4. Create a New Script Virtual User scripts can be created by using a script recorder, from a standard template, or by importing an existing source file. In these instructions we will be creating a Virtual User script from a recording.to record a new Script: a. Right-click on "Recordings" in your Project and select "New Recording..." or choose the "New Recording" button on the toolbar. b. Provide a name for your recording and select Web Proxy Recorder from the drop down menu and click "Next". 25

26 Choose the web browser from the drop down list against which you would like to record your script and click "Next". 26

27 c. Click Start Recording on the guide dialog. 27

28 d. The specified web browser and the recorder UI will appear. e. In the web browser, perform the actions that should be included in your first transaction. f. In the recorder UI, enter a name in the "Set Transaction" field for the second transaction you would like to record and then click "Set Transaction". Note: The first transaction is set automatically and will be called Start, as shown below. 28

29 g. Perform the actions on the web browser that should be included in the second transaction. h. Repeat the two previous steps until you are satisfied with the content of your recording. i. Click "More >>>" to the expand the recorder UI and review your transactions. j. Click the Stop button on the recorder toolbar, or click the close button on the recorder, to end the recording. k. Click "OK" to confirm you would like to end the recording. l. Click Next to continue. m. Use the Filter hosts panel to specify which hosts you would like to have included in your final script and click "Next". 29

30 n. Click Finish to continue to script generation. 30

31 5. Generate a Script From Your Recording Recording a Web session simply creates a raw recording. This recording is processed by the eggplant Performance Web script generator to create the final Web script. To generate a script from your recording: a. Choose the language in which you would like your script generated and click Next. b. Select your Web Virtual User from the list and click Next. c. Select the transactions from your recording that you would like to include in the generated script. d. Click the green plus to add a new generation rule for your Virtual User. Generation Rules allow one to automatically handle tasks such as parameterization, correlation, and validation each time a new script is generated. 31

32 e. Select the Verify Contains rule type from the drop down. This Generation Rule type is relevant to any recording regardless of the specific content of the recording. Click View Recording to view the filtered recording. f. Review the recording to determine the literal string you want to verify, and where in your recording it occurs. In this example, the phrase Sign up for a free trial today. g. Enter the literal string that you would like to verify during replay and click Next. 32

33 h. From the drop-down select the action that you would like to occur if the content cannot be verified. For example, Generate a warning message and continue will cause a warning message to appear in the run-time results, but the execution will otherwise continue. Click Next. i. Click the green plus to create a request filter that limits the requests to which your generation rule is applied. j. Review the matching requests and adjust the request filters until the desired requests are displayed. k. Click Next to continue. l. Review the summary of your new generation rule and click Finish to add your completed rule. 33

34 m. Click Next and then click Generate to generate your script. n. Once the script is finished generating, review the generation rules that were applied and click Finish. o. Your new script will appear under "Scripts" in your project. Record and generate at least one more script so that you can later create a Workflow. 6. Create a Workflow It is possible to create a simple test consisting of one script directly, without using a Workflow. However, using a workflow gives you a greater degree of control over your scripts when running a test. In a workflow, scripts can be placed in 3 different categories: initial, repeated, final. Scripts placed in the initial section will only be run once at the start of a test. Scripts in the repeated section are iterated multiple times as specified in VU Group Runtime Settings, and final is the last script to be run once at the very end. To create a Workflow: a. Right-click the "Workflows" header and select "New Workflow". b. Give your Workflow a name. c. Select your Web VU from the "Virtual User Type" drop-down list, which displays the associated scripts in the left pane. 34

35 d. Build the desired Workflow from your scripts using the Initial, Repeated, and Final selectors, and then click "OK". 7. Create and Configure a Test Designing a test allows you to configure how your Virtual User scripts will be used during the execution. A set of scripts can be reused and configured in different ways to allow an infinite number of different tests. 35

36 To create and configure a test: a. Right-click the new Workflow and select "Create Test". b. Select the Virtual User (VU) Group for your new Workflow and click the edit button. c. On the "Virtual Users" tab, increase the number of Virtual Users in the VU group to a conservative number, such as 5, as to not tax the localhost Injector. Also be mindful of the maximum Virtual Users allowed by available licenses. d. On the "Runtime Settings" tab, raise the number of iterations to 20 to increase the amount of data gathered and available for later analysis, and click "OK" to commit the changes. 36

37 8. Build your Project You must build your project to ensure it compiles correctly. To build your project: a. Click the "Build" button the toolbar to build your project. b. Confirm that the build was successful. Executing an eggplant Performance Test Executing an eggplant Performance Test This article provides step-by-step instructions to execute an eggplant Performance test. It focuses on the functionality of the eggplant Performance Test Controller. 37

38 Once you configure the parameters of your test and have successfully built your project in eggplant Performance Studio, you will be able to execute your test very easily from Test Controller and also view the behavior of the Virtual Users in real-time. 1. Open the Test Controller Right-click your Test and select "Open Test in Test Controller". This will launch the separate eggplant Performance Test Controller application. 2. Set up Charts for Viewing During Execution a. Right-Click on "Charts" and select "Edit Charts" from the menu. b. Click "Add..." to add charts. c. Select the charts you'd like to view during execution. 38

39 d. After selecting the charts of interest, click "OK". e. Click "OK" again on the Create Chart panel to dismiss it. Select "Charts" from the Test Explorer at any time during the test execution to view your charts as they update in real time. 39

40 3. Execute your Test a. Click "Start a new test run" on the toolbar. b. If you do not already have a Test Series, create one by giving the test series a name. Then, click "Start Test" to execute the test. 40

41 4. View Virtual User Event Logs During Execution a. Click the VU Group you want to view. (See 1 in the screenshot below.) b. Double-Click the VU you want to view.(see 2 in the screenshot below.) 5. View Virtual User Web Log 41

42 a. Double-click the globe icon for a particular Virtual User to open the Web Log or right-click and select "View Web Log..." b. Navigate the Web Replay panel for detailed information about actual web Requests and Responses. Viewing eggplant Performance Test Results Viewing eggplant Performance Test Results This portion of the step-by-step guide focuses on the functionality of the eggplant Performance Analyzer application to transform the raw data from your test into charts, providing a graphical representation of the results. eggplant Performance Analyzer provides reports that contain both charts and test results summary information. 1. Create an Analysis Database When the execution of your test completes, the "Test Complete" panel will appear. a. Ensure "Save the results of this test run" is selected. Optional to select "Launch Run Summariser when this dialog closes" and/or "Flag this text run for later analysis". In this example, we'll select "Flag this test run for later analysis". 42

43 Click "OK" to dismiss the panel. b. Click the "Analyzer" button from the toolbar in Test Controller. This will launch the separate eggplant Performance Analyzer application. c. Select the test run from the Results tree and click the "Analyze Raw Results" button in the toolbar. d. Advance through the "Create Analysis Database" wizard with the default settings. Click "Finish". 43

44 2. Create a View of the Database Advance through the "Create Test Data View" wizard with the default settings. Clicking "Next >>" at the "Confirm Options" stage will create the view. 44

45 3. Review Charts for the View Expand the View tree and double-click on a chart title to view the chart. 4. Create an Overlay Chart a. Right-click the chart title for which you'd like to create an overlay. b. Select the chart you would like to overlay and click "OK". 45

46 c. The overlay chart appears under "Custom charts" in the View tree. 5. Create and View a Report a. Right-click your view and select "Create HTML Report..." or "Create Word Report...". 46

47 b. Select the charts you want to have included in your report and click "OK". c. Select a location to save your report and give it a name. Click "Save". d. When the creation of the report completes, click "View Report". 47

48 Powered by Drupal Source URL: Links [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] 48