Performance Testing Process Overview

Components and Process for Automai's Performance Testing Solution: AppLoader

AppLoader Components

A load test configuration consists of an Apploader Controller, one or more Injectors, ScenarioBuilder, and the system (application) under test.

Performance Testing Process Overview (222492768)_alarch

AppLoader Controller: The central console from which tests are managed and monitored in real-time. Includes the report writer which generates summarized and detailed test analysis through reports and graphs.

Injector: The Windows server which hosts multiple rUsers sessions performing real life scenarios on the application under test. In a typical test setup, one or more Injector(s) run on a Windows Server. For large tests (thousands of simulated users), you can connect multiple Injector(s) to the AppLoader Controller by cloning one Injector.

ScenarioBuilder: The easy-to-use tool which facilitates the creation of a wide range of test scenarios for performance testing.

Note: If you have not installed AppLoader Suite (AppLoader Controller, Injector, and ScenarioBuilder) yet, please do so before continuing.

Tip: To view installation steps, please refer to the AppLoader Installation Guide.

Performance Testing Process Overview

Creating Test Scenario

Begin the performance testing process by determining the sections of application you want to emulate. You then develop these sections into scenarios by creating the same types of requests that your application invokes on the server. Each section will have its own scenario. ScenarioBuilder lets you easily create full-function scenarios.

Validating and Sending Test Scenario

When you are done with creating your test scenario(s), you need to send them to the Controller. But before sending, you should individually validate the scenario(s) you plan to use by playing them on the ScenarioBuilder. If the scenario runs to the end without any errors and runs multiple times without errors, it is valid to use in a load test. If the scenario aborts on an error, debug the scenario and run it through a simple test again.

Creating Test Plan

In the AppLoader Controller, when you plan your test, you need to specify some elements such as which scenario(s) to run, the number of simulated users that will run each scenario, the time all users will actively play scenarios, etc. All these factors can help to better emulate real-system activity. 

Running Load Test, Monitoring and Analyze Results

While a test is running for multiple users via the Injector(s), you can dynamically view overall load test as well as individual scenario execution on each user. AppLoader Controller collects application response times and back-end metrics, and provides test analysis through summarized and detailed reports and graphs. After executing the test, you can also view and export load test output data to spreadsheet or text documents for further analysis.