メインコンテンツまでスキップ
バージョン:26.2

Methods for Managing SUT Connections in Eggplant Test

Eggplant supports different methods for connecting to systems under test (SUTs) so you can optimize your test processes. You can create permanent, reusable, named connections, and temporary connections that you create and use just for the duration of your test runs.

The Three Methods for Connecting to Systems Under Test (SUTs)

There are three methods you can use to create and manage system under test (SUT) connections in Eggplant Test applications.

1. Create Connections within the Eggplant Test Apps

Create SUT Connections within Eggplant Test appsCreate SUT Connections within Eggplant Test apps

You can create, edit, delete, and establish SUT connections on connection configuration panels or pages within the apps. These "connection definitions" you name and save are typically permanent, meaning you can reuse them until you explicitly delete them. See Adding Connections in Eggplant Applications for more information.

2. Create Connections within a SenseTalk Script

Create a connection within a scriptCreate a connection within a script

You can create and establish a connection within in a SenseTalk script using the connect command. You can either create the connection in the script as part of the command, or connect to an existing SUT by specifying its name. The Eggplant Test product will connect to the SUT at runtime when the script runs the connect command, if it is not already connected. See Creating Connections from within a SenseTalk Script for more information. Note that SenseTalk is the Eggplant Test scripting language.

3. Create Connections at Test Runtime through a Command-Line Interface (CLI)

Create a Connection at Test Runtime through a Command-Line Interface (CLI)Create a Connection at Test Runtime through a Command-Line Interface (CLI)

You can create and establish a connection by passing parameters with the tests run through a command-line interface (CLI) with the runscript command. The runscript command invokes the Eggplant Fusion Engine (basically Eggplant Functional without is GUI interface) to run a test script. Connections created with tests run at the CLI are temporary, persisting only for the duration of the test run. See Creating Connections at Runtime through the Command Line Interface (CLI) for more information.

Next Step: Add a Connection in Eggplant Test

Continue to the page that describes the method you want to use to create a connection for your test type: