Eclipse Integrated Test Environment for SAP Agentry applications
If you have started using SMP SDK 3.0 SP06, you have a cool new option of testing your SAP Agentry mobile apps right from the new eclipse Test environment view. This is an alternative to the standalone Agentry Test Environment. With the introduction of this new eclipse view, I believe SAP’s intention is very clear. I believe, they would like to move all app testing to Eclipse some time in future.
Integrated test environment is included with the Agentry Editor and is installed automatically when you install Agentry Editor. This feature is available in SMP SDK 3,0 SP06.
Integrated Test Environment allows you to start and stop the test client, send a transmit; view data; view logs; and testing locales. Integrated test environment does not support test scripts.
Here is the information you need to get started with Integrated test environment view. This one talks only about getting up and running with the view and does not explore the different features.
In the eclipse environment choose Window=>Show View => Other => Agentry Views => Test Environment
You will notice that there is an issue with the Test Environment view. To overcome this we need to add an argument as per the information provided.
If you have never modified the eclipse.ini file, here are some important points to keep in mind:
- The -vm option and its value (the path) must be on separate lines.
- The value must be the full absolute or relative path to the Java executable, not just to the Java home directory.
- The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM
- For the 32-bit Eclipse executable (eclipse.exe on Windows) a 32-bit JVM must be used and for the 64-bit Eclipse executable a 64-bit JVM must be used. 32-bit Eclipse will not work with a 64-bit JVM
The file eclipse.ini can be found in the Eclipse folder(In the same folder as eclipse executable application)
The default eclipse.ini will look like this.
Please find a suitable jvm.dll and then add the vm argument before vmargs as shown here :
After restarting the eclipse, you will notice that the error has gone.