1.3 - Installation and Configuration

• Installation and Configuration
• Set Up an AWS RDS MySQL Instance for AIQ
• Configure AIQ Test Node Settings
• Obsolete Flex Flash SWF Configuration Reference
• Installation and Configuration FAQ
• Best Practices to Improve AIQ Performance
• Installing and Configuring Desktop Designer
• Installing and Configuring Desktop Designer
• Roku Environment Setup
• Windows AIQ Driver Setup
• Configure Open Broadcaster Software for AIQ Test Evidence
• Set Up Roku Remote Control for AIQ Testing
• Set Up Deep Link Tester for AIQ Mobile Testing
• Arrange Applications for Reliable AIQ Desktop Testing
• Troubleshoot Possible AIQ Performance Issues
• Cloud Configuration
• Cloud Configuration for AIQ Environments
• Test Deployment in a Cloud
• AIQ Cloud Architecture Overview
• Features and Benefits
• Cloud Testing Options
• Configure Scriptless Test Deployment
• Cloud Configuration FAQ for AIQ
• Load Runner
• Legacy LoadRunner Integration Overview
• Legacy LoadRunner Download Reference
• LoadRunner Installation for AIQ Integration
• Legacy LoadRunner Script Creation Reference
• Run Legacy LoadRunner Scripts in AIQ
• Evaluation Guides
• AIQ Evaluation Guides
• Working with Test Designer
• Work with TestNG Scripts in AIQ
• Run SoapUI Scripts as Functional Tests in AIQ
• Run SoapUI Scripts as Performance Tests in AIQ
• Run JMeter Scripts as Functional Tests in AIQ
• Run JMeter Scripts as Performance Tests in AIQ
• Work with HAR Scripts in AIQ
• Record a Scenario Editor Test
• Legacy Functional Scenario Creation Reference
• Legacy Performance Scenario Creation Reference
• Legacy App Pen Scenario Creation Reference

Installation and Configuration

This section describes installation procedures, configuration, deployment options, and options to integrate Appvance IQ (AIQ in short) into your software development life-cycle, production monitoring, and build environment.

For System Requirements, Install Guides, Evaluation Guides - Please refer to Getting Started with Appvance IQ.

The following sections detail more information:

Set Up an AWS RDS MySQL Instance for AIQ

Recommended guidance

Set up AWS RDS MySQL for AIQ only after confirming the supported database version, network architecture, security groups, parameter group settings, backup policy, and operational ownership.

Configuration checklist

• MySQL version, instance class, storage, Multi-AZ, backup retention, and maintenance window.
• VPC, subnet group, security group, DNS, TLS, and connectivity from AIQ hosts.
• Parameter settings required by AIQ, including packet size and case behavior where applicable.
• Database user permissions, rotation, monitoring, and restore process.

Validation workflow

1. Test connectivity from the AIQ application host.
2. Install or migrate the AIQ schema using approved scripts.
3. Run AIQ smoke tests for login, scenarios, Service Suite, and reports.
4. Document final endpoint, parameter group, backup, monitoring, and owner details.

Last updated: October 7, 2026

Configure AIQ Test Node Settings

Use this article to review AIQ Test Node settings that affect execution capacity, browser availability, connectivity, and result collection.

What changed in this article

• Normalized “TestNode” to “Test Node” and scoped the page to AIQ execution settings.
• Added checks for node identity, controller connection, browser/runtime paths, capacity, working directories, logs, proxy/certificate configuration, and heartbeat.
• Added validation guidance to run a small scenario after changing node settings.

Validation workflow

1. Review the node role, controller URL, browser/runtime availability, and execution capacity before changing settings.
2. Update only the required setting and restart the affected service if needed.
3. Run a small execution and confirm heartbeat, logs, output, and results collection.

Review note: This page now focuses on operationally safe Test Node setting changes.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Obsolete Flex Flash SWF Configuration Reference

This page is retained only to flag that Flex, Flash, and SWF configuration is obsolete for current AIQ testing.

What changed in this article

• Marked Flex/Flash/SWF configuration as obsolete because Flash-era browser technology is retired.
• Removed the impression that new AIQ environments should configure Flash or SWF support.
• Added migration guidance toward supported web technologies and modern browser execution paths.

Validation workflow

1. Do not configure new AIQ environments for Flash or SWF execution.
2. Confirm whether any remaining customer workflow still depends on retired Flash technology.
3. Document the dependency as legacy risk and plan migration to supported application technology.

Review note: This page is a strong deletion/archive candidate unless a customer requires historical context.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Installation and Configuration FAQ

Use this FAQ for current AIQ installation and configuration questions that do not require a dedicated procedure page.

What changed in this article

• Renamed the generic FAQ title so it is clear which book/context it belongs to.
• Reframed the FAQ as a routing and troubleshooting aid for installation/configuration topics.
• Added checks to avoid duplicating content that belongs in dedicated upgrade, Test Node, certificate, browser, or performance pages.

Validation workflow

1. Use this FAQ for short installation/configuration answers only when a dedicated article does not already cover the topic.
2. Link to the canonical procedure page when the answer requires multiple steps or risk controls.
3. Review FAQ entries periodically and promote repeated issues into standalone articles.

Review note: This page now has a clear scope and should not become a dumping ground for unrelated topics.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Best Practices to Improve AIQ Performance

Best Practices to Improve AIQ Performance

Use these practices to keep AIQ executions stable and results reliable. Performance tuning should consider the AIQ Controller, Test Nodes, database, browser capacity, network path, and the application under test.

Execution practices

• Validate scenarios with a small run before scaling load.
• Use realistic ramp-up and ramp-down periods.
• Keep test data reusable, resettable, and separate from scenario logic.
• Avoid unnecessary fixed waits; use Scenario Editor conditional waits where possible.

Environment practices

1. Size Test Nodes for the execution type and expected browser or user count.
2. Monitor CPU, memory, disk, network, and browser/driver health during large runs.
3. Keep AIQ, browser, driver, and operating-system versions aligned with release guidance.
4. Document environment changes before comparing performance results.

Last updated: September 18, 2026

Installing and Configuring Desktop Designer

Installing and Configuring Desktop Designer

Roku Environment Setup

Windows AIQ Driver Setup

Windows AIQ Driver Setup

Use this page when preparing a Windows machine to run AIQ browser, desktop, or device-related automation that depends on local drivers. Match driver versions to the target browser, operating system, and AIQ environment.

Preparation

• Install drivers with an account that has the required Windows permissions.
• Confirm the driver version matches the browser or application version used by the test.
• Store drivers in a controlled path and document that path in the environment configuration.
• Allow the driver through endpoint protection only when approved by IT or the customer security policy.
• Restart related services or the machine when the driver installation requires it.

Validation workflow

1. Run a basic AIQ smoke test that starts the target browser or desktop application.
2. Confirm the driver process starts and stops cleanly.
3. Review output logs for path, permission, or version mismatch errors.
4. Record the driver version and installation path for future upgrades.

Last updated: October 8, 2026

Configure Open Broadcaster Software for AIQ Test Evidence

Configure Open Broadcaster Software for AIQ Test Evidence

Open Broadcaster Software (OBS) can be used to capture video evidence while AIQ tests run. Use it when a team needs visual proof of application behavior, playback issues, or environment-specific failures.

Setup guidance

• Install a supported OBS version on the machine where the browser, desktop app, or device stream is visible.
• Create a dedicated scene for AIQ evidence capture and include only the required window, display, or device feed.
• Set the output path to a location with enough disk space for the planned run duration.
• Use a recording format that can be recovered if the session stops unexpectedly.
• Mask or avoid capturing credentials, customer data, and unrelated desktop content.

Validation workflow

1. Start a short recording before the AIQ run.
2. Run a small scenario and confirm the video shows the relevant application state.
3. Check audio, resolution, timestamps, and file size.
4. Attach or reference the recording with the related execution evidence.

Last updated: October 8, 2026

Set Up Roku Remote Control for AIQ Testing

Set Up Roku Remote Control for AIQ Testing

Use this guidance when AIQ tests need to control or validate a Roku-based application flow. Keep device setup consistent so remote-control actions are repeatable across test runs.

Setup checklist

• Confirm the Roku device and test controller are on the required network and can reach each other.
• Verify the app build, channel, or sideloaded package before running the scenario.
• Use a dedicated test account and reset application state when needed.
• Document the remote-control commands used by the scenario and the expected screen after each action.
• Capture device logs or screenshots when troubleshooting navigation failures.

Validation workflow

1. Pair or configure the remote-control method for the target device.
2. Run a short navigation smoke test.
3. Confirm that AIQ can detect the expected screen or application response.
4. Record any network, pairing, or device-state requirements in the test notes.

Last updated: October 8, 2026

Set Up Deep Link Tester for AIQ Mobile Testing

Set Up Deep Link Tester for AIQ Mobile Testing

Use a deep link tester when an AIQ mobile test needs to launch an app into a specific route, screen, or state. Deep links should be validated before they are added to repeatable mobile scenarios.

Prerequisites

• Confirm the app build installed on the device or emulator supports the target scheme, universal link, or app link.
• Document the exact deep link format, required parameters, and expected landing screen.
• Use test accounts and non-production data when validating app navigation.
• Reset the application state between runs when the deep link depends on login, cache, or stored preferences.

Validation workflow

1. Open the deep link manually on the target device and confirm the expected screen appears.
2. Add the deep link launch step to the AIQ mobile flow.
3. Run the test once with logging enabled and capture evidence.
4. Add assertions for the landing screen so failures are detected immediately.

Last updated: October 8, 2026

Arrange Applications for Reliable AIQ Desktop Testing

Arrange Applications for Reliable AIQ Desktop Testing

Arrange desktop applications consistently before an AIQ desktop test runs. Predictable window placement helps reduce failures caused by hidden controls, overlapping windows, or unexpected screen resolution changes.

Recommended setup

• Use a dedicated test machine or session for desktop automation.
• Set the display resolution and scaling before recording or running tests.
• Open only the applications required by the scenario.
• Place the application under test in a known position and avoid overlapping windows.
• Disable pop-ups, notifications, and screen savers that can cover the application.

Validation workflow

1. Start from a clean desktop session.
2. Open the required application and arrange it as expected.
3. Run a short smoke test that validates the first interaction and a key screen state.
4. Capture a screenshot if the arrangement is part of the support procedure.

Last updated: October 8, 2026

Troubleshoot Possible AIQ Performance Issues

Troubleshoot Possible AIQ Performance Issues

Use this article when AIQ feels slow, executions queue unexpectedly, reports load slowly, or test nodes are not keeping up with scheduled demand. Start with environment evidence before changing configuration.

Common areas to review

• Host resources: CPU, memory, disk I/O, and available storage on controller, database, and test-node hosts.
• Database health: Result-table growth, slow queries, retention settings, and backup activity.
• Test-node capacity: Number of concurrent executions, browser/device availability, and node connectivity.
• Scenario design: Excessive waits, unnecessary screenshots, large payloads, and missing cleanup steps.
• Network path: Latency or firewall issues between AIQ services, test nodes, databases, and target applications.

Recommended workflow

1. Capture the exact symptom, affected time range, and AIQ components involved.
2. Review logs and resource metrics before restarting services.
3. Run a small known-good scenario to separate platform issues from scenario-specific issues.
4. Apply one change at a time and record the result.

Last updated: October 8, 2026

Cloud Configuration

Cloud Configuration for AIQ Environments

Last reviewed: September 22, 2026

Use this page as an overview for AIQ cloud environment configuration, including network, security, scaling, and integration dependencies.

Recommended guidance

• Confirm cloud provider, region, sizing, and network topology.
• Use infrastructure standards for secrets, certificates, backups, and monitoring.
• Validate test nodes and controller connectivity before running production workloads.

Validation workflow

1. Review the architecture and system requirements for the target AIQ version.
2. Configure networking, DNS, TLS, firewall rules, and storage according to the deployment plan.
3. Connect test nodes and required integrations.
4. Run smoke tests for sign-in, scenario execution, reporting, and monitoring.
5. Document operational ownership, backup, scaling, and incident procedures.

Note: Cloud configuration details vary by provider and AIQ version; use this page as an overview, not a substitute for the deployment runbook.

---

Last updated: September 22, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Test Deployment in a Cloud

AIQ is a distributed test environment. AIQ runs your tests on a Grid of your test equipment, in a Cloud Computing environment, or both.

AIQ provides specific commands to support the automatic deployment and operation of your tests in a grid of servers and a Cloud Testing environment. For example, identify a cloud testing service like Amazon EC2 in a Test Scenario. AIQ creates the Test Nodes in EC2 instances, runs the test, retrieves the results, and takes down the EC2 instances. AIQ deploys and operates tests in a "lights out" manner for full Cloud Test automation.

Appvance IQ works on-premises behind your firewall or in your favorite cloud environment, or both in hybrid mode. It supports integration with the following:

1. Amazon Web Services

2. IBM Softlayer

3. OpenStack Cloud Software

AIQ Grid technology works in your QA lab, in the Cloud, or both. Identify a set of TestNodes running in your QA lab to AIQ. AIQ automatically selects the available TestNodes to deploy and operate your tests.

Appvance provides Test OnDemand Testing as a Service (TAAS) services to host your tests.

AIQ Cloud Architecture Overview

AIQ Cloud Architecture Overview

AIQ cloud deployments use controller, execution, storage, and integration components sized for the target workload. Exact architecture depends on the customer environment, deployment model, and AIQ release.

Core areas

• Controller services coordinate users, projects, executions, and reporting.
• Execution capacity is provided by Test Nodes or equivalent worker resources.
• Storage and data services retain configuration, execution results, and operational test data.
• Networking, certificates, proxy rules, and integrations connect AIQ to the systems under test.

Operational checklist

1. Document ports, domains, certificates, and proxy requirements.
2. Size execution capacity for the expected browser, service, mobile, or performance workload.
3. Monitor controller, database, and Test Node health during high-volume runs.
4. Review security, access, backup, and retention requirements with the environment owner.

Last updated: September 18, 2026

Features and Benefits

Cloud Computing and AIQ Grid technology provide huge new benefits to app performance solutions:

• Run At User Levels Never Before Possible - Building a test lab used to be prohibitively costly for medium and large-scale load tests. Cloud computing delivers bandwidth and computing power to achieve tests in the millions-of-users levels at commodity prices

• Run From Multiple Locations Around The World - Cloud Testing environments are a worldwide phenomenon. AIQ runs tests in multiple Cloud Testing environments. This makes it possible to manage performance from your user's geographic location

• Pay As You Go, Pay Only For What You Need - Cloud Testing eliminates the cost of building and maintaining a test lab for load and performance testing. No longer is there a need to provision expensive and difficult to manage quality test labs. Appvance Cloud Testing lets you pay as you operate tests.

• Ideal for automating test operation from a Continuous Integration environment. The CI platform starts a Test Scenario test and AIQ automatically provisions and deploys tests to the available TestNodes in your own Grid or in a Cloud Testing environment

• Test In Your Environment, In A Cloud Environment, Or Both - Appvance delivers ultimate flexibility

Cloud Testing Options

Appvance IQ provides several options for running tests in a Cloud Testing environment. These options are configured in a TestScenario and determine how AIQ provisions, uses, and manages TestNode instances during test execution.

The Scenario Builder supports the following Cloud Testing settings.

Name

The Name identifies the Cloud Testing environment configuration used to manage the cloud resources.

Type

The Type specifies the cloud environment to use. Available options include:

• EC2
• SoftLayer
• Grid
• OpenStack

Beginning

The Beginning setting determines how Appvance IQ provisions or starts TestNode instances when staging the test.

Available options are:

1. Create All — Creates new instances for all required TestNodes.
2. None — Does not start or create any instances.
3. Create Required — Uses available running instances and creates new instances only when additional machines are required.
   For example, if three machines are required and one is already running, AIQ uses the existing machine and creates the remaining two.
4. Start All — Starts all stopped instances. This option requires all machines to be stopped. If some machines are already running while others are stopped, an error may occur.

End

The End setting determines what Appvance IQ does with the TestNode instances when the test finishes.

Available options are:

1. Terminate All — Terminates all instances.
2. Started — Terminates only the instances that were started for the test.
3. None — Does not terminate or stop any instances.
4. Stop All — Stops all running instances.

Reboot

The Reboot setting determines whether AIQ reboots TestNode instances after test execution.

Rebooting can help release resources when an application under test leaves network connections open or otherwise prevents resources such as memory and network connections from being released properly.

Available options are:

• After — Reboots the node after the test. AIQ does not reboot machines that have already been terminated.
• Never — Does not reboot the node after the test.

All Available Machines

All Available Machines specifies the desired number of TestNode instances available for the test.

Config

Config specifies the path to the AIQ Cloud Testing configuration file.

The configuration file contains the cloud access credentials, security keys, and account preferences required to access the selected Cloud Testing environment.

Network Bandwidth

Network Bandwidth specifies the network bandwidth, in Kbps, to use for tests running in the specified location.

Username and Password

Username and Password specify the credentials used to log in to the TestNode machine.

These credentials should correspond to the original credentials of the machine used to create the AMI.

If the default credentials were used when creating the AMI, leave these fields blank.

---

Last updated: August 19, 2026

If you have any feedback on this topic, please contact us at documentation@appvance.ai.

Configure Scriptless Test Deployment

Configure Scriptless Test Deployment

Use scriptless test deployment configuration to prepare Scenario Editor tests for execution in the intended AIQ environment. Keep deployment settings aligned with the target environment, Test Node capacity, browser support, and test data strategy.

Before deployment

• Confirm the target environment, browser or device requirements, and Test Node availability.
• Validate test data and credentials using approved secure configuration methods.
• Review scenario waits, locators, and validations for maintainability.
• Run a focused validation execution before adding the test to a larger suite.

Deployment notes

1. Document environment-specific settings and avoid hard-coding them into steps.
2. Keep reusable data in DPLs or approved data sources.
3. Review output after the first scheduled or suite execution.

Last updated: September 18, 2026

Cloud Configuration FAQ for AIQ

Last reviewed: September 25, 2026

Use this FAQ to answer common AIQ cloud configuration questions without duplicating provider-specific setup steps.

What changed in this article

• Moved the FAQ toward cloud/grid decision points instead of old one-off provider instructions.
• Clarified when to use cloud execution, grid execution, or local test nodes.
• Added checks for credentials, network reachability, browser availability, and capacity before troubleshooting a cloud run.

Validation workflow

1. Identify whether the question is about cloud provider setup, grid capacity, or node connectivity.
2. Verify credentials, routing, firewall rules, and browser versions before changing AIQ settings.
3. Use a small validation run before scaling to a full cloud execution.

Review note: Connected this FAQ to the newer cloud/grid configuration articles and treated old provider-specific details as legacy.

---

Last updated: September 25, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Load Runner

Legacy LoadRunner Integration Overview

Last reviewed: September 29, 2026

Use this overview only when an AIQ environment still needs to reference LoadRunner integration concepts or migration details.

What changed in this article

• Marked the broad Load Runner page as legacy overview content.
• Connected the overview to the separate LoadRunner script creation, download, admin, and execution pages instead of duplicating steps.
• Added decision guidance for when to keep LoadRunner support versus migrate to AIQ-native or JMeter-based workflows.

Validation workflow

1. Confirm why LoadRunner is still required for the environment.
2. Identify whether the work involves script creation, software download, admin configuration, or execution.
3. Route the user to the specific LoadRunner page and document any migration plan.

Review note: This page now acts as an overview/router instead of a generic placeholder.

---

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Legacy LoadRunner Download Reference

Last reviewed: September 29, 2026

This page is retained as a legacy reference for locating and preparing LoadRunner software in environments that still depend on it.

What changed in this article

• Marked the download instructions as legacy because LoadRunner availability, licensing, and vendor download paths can change.
• Added checks for license ownership, version compatibility, installer source, checksum/security review, and supported operating system.
• Added a warning not to download installers from unapproved third-party locations.

Validation workflow

1. Confirm the approved LoadRunner version and license with the customer or tool owner.
2. Use the vendor-approved download path and validate the installer before use.
3. Record version and install location before configuring AIQ integration.

Review note: This page now avoids hard-coding stale vendor download guidance.

---

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

LoadRunner Installation for AIQ Integration

Recommended guidance

Install LoadRunner components for AIQ only when the integration is still required by the customer’s performance workflow. Confirm product versions, licensing, operating system support, and ownership before changing the environment.

Before installation

• Confirm AIQ version, LoadRunner version, Windows/Linux host, and integration objective.
• Verify licensing, installers, checksums, and approved download sources.
• Review firewall, proxy, certificate, antivirus, and account permissions.
• Back up existing performance-test configuration and scripts.

Validation workflow

1. Install in a non-production or controlled environment first.
2. Run a small functional smoke test before load execution.
3. Confirm AIQ can invoke or exchange data with the LoadRunner assets as intended.
4. Document version, install path, service accounts, and rollback steps.

Last updated: October 6, 2026

Legacy LoadRunner Script Creation Reference

Last reviewed: September 29, 2026

This page is retained as a legacy reference for teams that still need to create LoadRunner scripts for AIQ-related workflows.

What changed in this article

• Marked LoadRunner script creation as legacy/environment-specific content rather than current default AIQ guidance.
• Added checks for protocol choice, correlation needs, parameterization, runtime settings, and data files before AIQ execution.
• Separated script creation from download/admin/runtime configuration, which are covered by the other LoadRunner pages.

Validation workflow

1. Confirm the customer still requires LoadRunner scripts before creating new assets.
2. Create or update the script with required protocol, parameters, correlations, and test data.
3. Run a small validation before connecting the script to AIQ execution.

Review note: Use this page only for legacy LoadRunner support or migration work.

---

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Run Legacy LoadRunner Scripts in AIQ

Last reviewed: September 29, 2026

Use this article when an existing LoadRunner script must be executed through AIQ for a supported legacy workflow.

What changed in this article

• Marked LoadRunner execution as legacy/environment-specific and separated it from script creation/download/admin setup.
• Added checks for script path, runtime settings, data files, controller/node access, licenses, and result collection.
• Added a validation step to run a small script before scheduling larger runs.

Validation workflow

1. Confirm the LoadRunner script and dependencies are available to the AIQ execution environment.
2. Validate runtime settings, data files, and any required licenses before execution.
3. Run a small execution and verify output/results before scaling or reporting.

Review note: This article now focuses on safe execution of existing LoadRunner assets.

---

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Evaluation Guides

AIQ Evaluation Guides

Recommended guidance

Evaluation guides should help users prove AIQ value through a focused, realistic, and repeatable workflow. Keep evaluation content current, scoped, and aligned with modern AIQ terminology such as Scenario Editor, Service Suite, AISG, and Test Nodes.

Evaluation planning

• Define business goals, success criteria, timeline, and stakeholders.
• Select representative web, mobile, API, performance, or data-driven scenarios.
• Prepare test data, accounts, applications, environments, and access ahead of time.
• Capture evidence through reports, logs, screenshots, and repeatable results.

Quality checks

1. Avoid broad demos that do not map to customer outcomes.
2. Use current product names and remove obsolete Designer or Blueprint wording when not historical.
3. Document assumptions, limitations, and follow-up actions.
4. Keep customer-specific evaluation notes out of public documentation.

Last updated: October 6, 2026

Working with Test Designer

Appvance Designer is a powerful code-free scripting environment that is included in Appvance IQ. In this lesson, you will learn how to use Test Designer Scripts (DS3) to load test a web application.

Pre-Requisite

This guide assumes you successfully completed Recording a Appvance Designer Script from Designer 3.0 or have a working Designer script.

About Appvance Designer Scripts

Designer scripts are captured using Appvance Test Designer, and easy and straightforward to modify, modularize and data-drive.

Designer Exercise 1

1. Go to your Appvance IQ URL and login
2. Select Build and click Scenario Editor
3. Select File and click New
   A new scenario appears with the Info tab selected, displaying the Scenario Test Type options. You will configure the scenario by selecting multiple tabs along the left, and supplying the requested information.
4. Click Please select a Test Type and select Functional Test
5. Select the Test Management tab
   For this example, we will only run the functional test case one time. Use this section in the future to indicate how many times to repeat each test case, as well as how many concurrent users you wish to allow.
6. Select the Test Cases tab
   The Test Case tab allows you to define test cases to run for each iteration. If we had indicated to repeat the scenario more than once, an equivalent number of iterations would exist.
7. Click Add a Test Case Execution
   Test Cases are a collection of one or more scripts, executed sequentially in the order you define. Any of the supported Script Types can be used together in a single Test Case. Scripts can also use, or share data (DPL) and browser sessions (Instances). Continue following our evaluation guides to learn more.
8. Enter a name in the Test Case Name box
9. Enter a name in the Script Name box
   Many times, test cases are a collection of scripts, where the test case name is different than a single script's name. We'll use only one script in this example, making the name potentially appear redundant.
10. Click the Script Type box and select Appvance Test Designer Script 3.0
11. In the Resource box, click Browse
    The Open window displays access to the Appvance IQ Server file system as well as any source control repositories configured in your user's Global Settings.
12. Select your Designer script containing the *.ds file extension and click Open
13. Click the Browser box and select the browser the scenario should use to run the script
14. Click Save
15. Select File and click Save
    The Save window display the same access to the Appvance IQ Server file system as well as your connected source control repositories.
16. Select a location to save the scenario, enter a name in the File Name box and click Save
    Your scenario is ready to run. Remember, your scenario runs on the indicated test node, which for evaluations is most commonly the same location as the Appvance UTP Controller. You will not visually witness the test execute, as it is executing on the test node, with a physical browser. You can however monitor results live and post execution.
17. Click Play Scenario
18. The scenario displays the live execution results
19. Once the execution completes, click Output and select Click here
    You can return to past executions by going to Analyze and selecting any prior execution
    Similarly, you can click Play, and open a currently running execution, run or edit the scenario
    
    

Designer Exercise2

1. Open Appvance IQ and login.
2. Click Build.
3. Select File > Open
4. Navigate to the Designer_example/Spree directory in the training examples.
5. Select spree_performance.scenario, and click Open.The Scenario Test Type is Performance Test
6. Select Test Management. Repeat scenario's test case is set to 1
7. Here you'll notice the Test Case is set to run with 2 users and 1 execution. This means two browser windows will open as separate users.
8. Click the pencil icon to edit the Test Case.The Script Type is set to Appvance Designer Script, and the test case Resource points to the spree_test.ds file located in the Designer_example/Spree directory. Additionally, here we have a Data Production Library (DPL) called 'Users' which is a CSV file containing a list of users the test will use to login to the Spree site.
9. Click 'Cancel'
10. Select 'Resources 'All resources related to the Scenario are summarized, including the test case and CSV called Testusers.csv for data driving at the bottom. This is the file containing the aforementioned users.
11. Click Play Scenario to execute the scenario.
12. The Scenario loads in new browser windows (two this time as two users) and executes the interactions recorded in the designer script.
13. Execution completion is indicated with Execution Done at the top.
14. Click Output, then Click Here at the bottom to see the reports generated.

Work with TestNG Scripts in AIQ

Last reviewed: September 29, 2026

Use this article when a TestNG script needs to be prepared, packaged, and executed from AIQ.

What changed in this article

• Moved the page from generic installation wording into a TestNG execution workflow.
• Added concrete checks for dependencies, testng.xml, classpath, JAR packaging, parameters, and browser/node compatibility.
• Clarified that TestNG scripts should be validated locally before being scheduled in AIQ.

Validation workflow

1. Build the TestNG project and confirm testng.xml points to the intended classes and parameters.
2. Package dependencies so the AIQ execution node can resolve them.
3. Run a small AIQ execution and compare failures with the local TestNG output.

Review note: Focused the article on execution readiness, not just “working with scripts.”

---

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Run SoapUI Scripts as Functional Tests in AIQ

Recommended guidance

Run SoapUI scripts as functional tests in AIQ only when a SoapUI asset remains part of the customer workflow. For new API automation, evaluate whether Service Suite can replace or simplify the legacy SoapUI dependency.

Before running

• Confirm SoapUI version, script location, dependencies, environment, and credentials.
• Use safe placeholders or approved secret storage for endpoints and tokens.
• Validate network, proxy, certificate, and firewall access from the AIQ host.
• Define pass/fail criteria and expected artifacts.

Validation workflow

1. Run the SoapUI script outside AIQ first to confirm it is valid.
2. Run a small AIQ functional test wrapper.
3. Review logs, return codes, assertions, and generated reports.
4. Document migration opportunities to Service Suite if the script is redundant.

Last updated: October 6, 2026

Run SoapUI Scripts as Performance Tests in AIQ

Recommended guidance

Run SoapUI scripts as performance tests only when the script, environment, and load model are suitable for repeatable load execution. Confirm whether Service Suite or native AIQ performance assets can provide a cleaner current workflow.

Performance considerations

• SoapUI script efficiency, setup/teardown behavior, and thread safety.
• Data uniqueness, account pools, cleanup, and external service rate limits.
• Load generator capacity, monitoring, and artifact size.
• Clear TPS, response-time, error-rate, and duration targets.

Validation workflow

1. Run a single-thread validation before adding load.
2. Increase concurrency gradually and monitor both AIQ and target systems.
3. Separate SoapUI script bottlenecks from application bottlenecks.
4. Document results, limitations, and migration options.

Last updated: October 6, 2026

Run JMeter Scripts as Functional Tests in AIQ

Last reviewed: September 25, 2026

Use this article when a JMeter script is being executed in AIQ for functional validation rather than load generation.

What changed in this article

• Clarified that functional JMeter runs should validate behavior, assertions, and transaction success, not virtual-user scalability.
• Added guidance to keep datasets small and expected results explicit.
• Separated functional execution from performance execution so teams do not interpret functional results as load-test evidence.

Validation workflow

1. Import or select the JMeter script and confirm assertions are present.
2. Run with a controlled user count and data set appropriate for functional validation.
3. Review output, assertions, and results before promoting the script to performance testing.

Review note: Reduced ambiguity between functional JMeter execution and performance JMeter execution.

---

Last updated: September 25, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Run JMeter Scripts as Performance Tests in AIQ

Last reviewed: September 25, 2026

Use this article when a JMeter script is executed in AIQ to generate load and measure performance behavior.

What changed in this article

• Clarified that performance runs require workload model, ramp-up, duration, and result interpretation.
• Added reminders to validate test data, target environment capacity, and monitoring before load generation.
• Separated performance-test guidance from the functional JMeter article so reports are interpreted correctly.

Validation workflow

1. Confirm the workload model, virtual-user target, ramp-up, duration, and data requirements.
2. Run a small shakeout before the full performance test.
3. Review throughput, response times, errors, and infrastructure monitoring after execution.

Review note: Focused this page on load/performance concerns instead of generic JMeter playback.

---

Last updated: September 25, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Work with HAR Scripts in AIQ

Last reviewed: September 29, 2026

Use this article when HAR network captures are converted, replayed, or validated as part of AIQ testing.

What changed in this article

• Clarified that HAR scripts are network-capture artifacts and not a substitute for functional assertions.
• Added checks for request ordering, dynamic tokens, cookies, headers, payload masking, and environment-specific URLs.
• Connected HAR usage to validation/storage workflows and security review before sharing.

Validation workflow

1. Review the HAR for sensitive headers, cookies, tokens, and customer data before reuse.
2. Validate that dynamic values are parameterized or regenerated during playback.
3. Run the HAR-based flow and compare network responses with the expected application behavior.

Review note: The page now treats HAR as a network-evidence artifact with security and dynamic-data constraints.

---

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Record a Scenario Editor Test

Record a Scenario Editor Test

This article replaces legacy Designer 3.0 wording with current Scenario Editor terminology. Use recording as a starting point, then review and maintain the scenario before adding it to a suite.

Recommended workflow

1. Prepare approved test data and a clean application state.
2. Record the shortest flow that proves the target behavior.
3. Review generated steps and replace fragile locators or fixed waits.
4. Add validations and stored values where they prove business behavior.
5. Run a small validation execution and review output before scaling.

Maintenance notes

• Do not keep obsolete Designer-only instructions in current AIQ documentation.
• Prefer clear scenario names and reusable data mappings.
• Use conditional waits instead of arbitrary pauses where possible.

Last updated: September 18, 2026

Legacy Functional Scenario Creation Reference

Last reviewed: October 2, 2026

This page is retained as a legacy reference for older Appvance Designer Script 3.0 functional scenario workflows.

What changed in this article

• Marked Designer Script 3.0 functional-scenario creation as legacy content.
• Added migration framing toward Scenario Editor for current functional scenario creation.
• Added checks for locators, waits, test data, browser support, and validation evidence before reusing legacy assets.

Validation workflow

1. Confirm whether the functional test can be rebuilt or maintained in Scenario Editor.
2. If the legacy workflow is still required, document the exact AIQ version and browser/runtime assumptions.
3. Replay the scenario and update locators, waits, and validations before considering it maintained.

Review note: This page should not be treated as the current functional-scenario creation path.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Legacy Performance Scenario Creation Reference

Last reviewed: October 2, 2026

This page is retained as a legacy reference for older Appvance Designer Script 3.0 performance scenario workflows.

What changed in this article

• Marked Designer Script 3.0 performance-scenario creation as legacy content.
• Added guidance to verify load model, test data, pacing, browser/runtime assumptions, and current AIQ execution support.
• Connected legacy scenario review to current performance-test readiness rather than blindly following old steps.

Validation workflow

1. Confirm the performance scenario still represents the current business workflow and load model.
2. Validate data, pacing, correlations, and execution-node capacity before running at scale.
3. Prefer current AIQ scenario creation paths for new performance work.

Review note: This page now signals legacy status and focuses on safe reuse only.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Legacy App Pen Scenario Creation Reference

Last reviewed: October 2, 2026

This page is retained as a legacy reference for older Appvance Designer Script 3.0 App Pen scenario workflows.

What changed in this article

• Corrected the title grammar and marked Appvance Designer Script 3.0 content as legacy.
• Replaced current-action wording with guidance to use Scenario Editor for new work where possible.
• Added checks for customer dependency, migration path, scenario ownership, and whether screenshots/data still match the old workflow.

Validation workflow

1. Confirm the workflow still depends on Appvance Designer Script 3.0 before following this page.
2. Prefer Scenario Editor for new scenario creation and document any blocker that requires legacy App Pen steps.
3. Validate the resulting scenario in the current AIQ environment before reusing it.

Review note: This page is a legacy bridge, not recommended setup guidance for new scenarios.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.