Skip to Content
Author's profile photo Søren Hansen

SMP 3.0: Agentry Integrated Test Environment


The new Eclipse based Integrated Test Environment, which takes over the functionalities of the old ATE (Agentry Test Environment), has been awaited for quite some time, and has been released for a while now. It is delivered in SMP 3.0 SDK SP06.

I have had a chance to try it out, and even though there is still room for improvements, I must say that it is a MAJOR leap in the right direction.

It is more or less a one-to-one migration of the old ATE to an Eclipse based Test Environment, meaning no new functionalities for inspection has been added. However there is one major difference: You can now interact with the UI for other platforms than the Windows based ones. The UI is using the WPF windows client, and when choosing a non-windows based OS, it will still render in the WPF UI.

Still it is not a perfect rendering of iOS and Android, as on native devices. Images and screen elements may appear differently in the Test Environment and the native device, both with regards to enablement, size, format and functionality. But it is very nice to be able to inspect data objects, rules and actions, while executing screen logic. As I said a major step in the right direction.

The usage of the Test Environment in Eclipse is a little clumsy in my opinion, and not well suited for execution in the same environment as you make Agentry and Java development. Therefore I would suggest to install it in a dedicated Eclipse environment.

Furthermore I hope that SAP in the future will extend its capabilities to support multiple sessions (Agentry applications and/or backends) in the same Eclipse environment.

Features of the Integrated Test Environment

The installation and setup of the Integrated Test Environment has been nicely described in the blog, so I will not elaborate on this.

Please note that you may have to install the WPF client to get the Integrated Test Environment to start up correctly. It seems to be a prerequisite, since the Integrated Test Environment is actually using the WPF client to render the UI.

Note on updating the Agentry Editor (Plugin):

When upgrading your (existing) Eclipse Environment to SP07 PL01 you will get some errors, if you have an older version installed already.

Perform these steps to successfully upgrade:

1. Close your Agentry Application Project (Right-click and choose Close Project).

2. Close the Test Environment view.

3. Restart Eclipse.

You can now successfully upgrade.

Startup of the Test Environment

The Test Environment will create some files for configuration and tracing, and these files requires an Agentry Project to exist and be open before you can start the Test Environment. There is no requirement that the project must be identical to Agentry Application you want to test, so it can be any Agentry project.


Warning that no open Project exists.


Menu item to start the Test Environment is inactive.

Create dummy Agentry project

To avoid any confusion I have created a dummy Agentry Project in my (dedicated) Eclipse Environment.

Simply choose File->New->Other…->Agentry Project->New Agentry Project, and create an Agentry application with no implementation.



After creation of the dummy application it is now possible to start the Test Client (Test Environment).

When starting the Test Environment you will need to provide credentials (username and password) as well as a URL to hit the Agentry instance on SMP.


After startup you will see this screen.

Click “Menu” to go to the application.

From here you can also export the local DB of the application, as well as reset the client.


In my case I am accessing a modified version of SAP Work Manager 6.1 which is displayed.

For the first time in Agentry history, it is possible to interact with the UI of an Android screen set 🙂

The Menus

Before you can access the menus you need to minimize the Application screen. If you are Alt-Tab’ing between screens, you must minimize every time you return to Eclipse.


You cannot minimize or hide this window.

This is the reasons why I call the implementation “clumsy”. It is not working smoothly, but still it is minor bugs.

After moving the screen out of the way you will gain access to the menus.



If you are familiar with the ATE, you will recognize all of the menu items, as they also existed here.

However a few notes on functionality:

  • I have not been able to get the Transaction display to function. Even when I am sure I have executed some Add Transactions, I don’t see the data in the Transactions view.
  • View for Complex Table no longer shows number of records in table, which is a little bit annoying.
  • The Clear Log… functionality does not work. You must delete the debug.log file in the package explorer to clear it.


Windows displayed by the Test Environment in Eclipse:

  • Top Left: The dummy Agentry Application.
  • Middle Left: Annoying window that cannot be minimized while inspecting a running application.
  • Top Middle: Debug log of an Action set for logging.
  • Bottom Left: Objects inspection.
  • Bottom Middle: Transaction inspection (which is always empty)
  • Bottom Right: Complex Table inspection.

All-in-all a very useful Agentry Integrated Test Environment.

There are some bugs to be fixed, but for a first version SAP has done a very good job.


Søren Hansen

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Soren, Thanks for the nice blog on the integrated ATE. I can open the test environment and also see the green "Start client" menu button. But after I click this button, nothing happens. Just wondering whether you have done any other config changes to make this work. Appreciate your help, Thanks - Raj Peddisetty.

      Author's profile photo Søren Hansen
      Søren Hansen
      Blog Post Author

      Hi Raj,

      Sorry, but as far as I remember I simply followed the mentioned guide, and don't recall to have seen this behavior. I am assuming you are not getting any errors or warnings in the Test Environment.


      Author's profile photo Former Member
      Former Member

      Raj, did you install the WPF client? Without that, you might see the behaviour you're describing.

      Author's profile photo Former Member
      Former Member

      You might miss some of the external components like .net framework.

      Best way like Morten said, install WPF client, it will include the check for .net framework.