2.8.1. General Information and setup for the Embedded Agent for tests with API
Prev | 2.8. Using the Embedded Agent for tests with API | Next

### 2.8.1. General Information and setup for the Embedded Agent for tests with API

It is possible that a AUT agent could be started within a Test. Therefore a test can be written and executed completely without an other Jubula application. All Toolkits, except HTML are supported.

General setup information

The following section describes where to find the relevant JARs / artifacts to use the EmbeddedAgent for API. The provided EmbeddedAgent has a minimum required runtime environment of Java 8 .

Following JARs / maven artifacts / OSGi bundles must be used in addition to the client API jars(see Chapter 2, Writing UI tests via client API.). These Jars must be on the classpath:

1. Each project requires dependencies to all of the toolkit neutral parts of the API:

   - org.eclipse.jubula.autagent.api

   - org.eclipse.jubula.autagent.common

   - org.eclipse.jubula.client.api

   - org.eclipse.jubula.toolkit.api

   - org.eclipse.jubula.rc.common.agent

   - org.eclipse.jubula.tools

   - org.eclipse.jubula.tools.exec

   - org.eclipse.jubula.communication

2. The following are 3rd party libaries which are needed on the classpath.

   - org.apache.commons.lang

   - org.apache.commons.io

   - org.apache.commons.exec

   - org.apache.commons.codec

   - org.apache.commons.beanutils

3. The following jars can be on the classpath but are not mandatory. But it is important that they are located in the same directory as the org.eclipse.jubula.autagent.api. The following is needed independent on the toolkit:

   - org.eclipse.jubula.rc.common

   Each project requires dependencies to individual parts of the toolkit specific elements dependent from the used toolkit of the API:

   - org.eclipse.jubula.rc.javafx

   - org.eclipse.jubula.rc.javafx.j8u40

   - org.eclipse.jubula.rc.swing

   - org.eclipse.jubula.rc.swt

   RCP is not listed because the rc.rcp plugin is deployed into the AUT

4. Each project also requires dependencies to all of the 3rd party dependencies of the API:

   - org.apache.oro

   - javax.xml

   - javax.xml.stream

   - org.slf4j.api

   - ch.logback.classic

   - ch.logback.core

   - org.xmlpull

   - com.thoughtworks.xstream

You can find the artifacts in different shapes (plain JAR and maven artifact) within the <ITEInstallationFolder>/development/api folder. To define OSGi dependencies to the API artifacts you can simply include the <ITEInstallationFolder>/development/org.eclipse.jubula.repo.zip in your target platform (definition) and define a dependency to the "Jubula Functional Testing - API Embedded"-feature.

A list of changes which happened over time in the API is located here .