Previous Topic

Next Topic

Book Contents

Book Index

SAP GUI testing guide

This chapter provides all the elements required to properly run SAP GUI applications tests.

In This Chapter

Prerequisites

Recording an SAP GUI application

Editing an SAP GUI User Path

Generating a higher load with Remote Desktop Services

Screenshots on error

FAQ

See Also

User guides

Best practices

Agile

Design process

Heavy load testing

Mobile testing

Oracle Forms applications testing

Integrate NeoLoad with third-party tools

Prerequisites

Before using the SAP GUI-compatible version of NeoLoad, the following requirements must be fulfilled:

Recording an SAP GUI application

  1. Before recording an SAP GUI application, the following requirements must be met:
  2. In NeoLoad, go to Record > Start SAP Recording. For more information, see Record an SAP GUI application.

Editing an SAP GUI User Path

After the User Path is recorded, you can insert Actions like ‘Read’, ’IsSelected', ‘IsObjectChangeable’ or ‘IsObjectAvailable’ to:

For more information, see SAP GUI Actions.

Generating a higher load with Remote Desktop Services

Machines running SAP GUI Virtual Users may be limited in the number of Virtual Users they can run, due to the graphic resources available to that machine.

You can generate a higher number of Virtual Users on high-end servers (high CPU, high memory) by using several Remote Desktop Services sessions on the same machine.

For more information about installation prerequisites, see the Terminal Services installation guide.

With NeoLoad

NeoLoad can remotely start as many Windows sessions as required on each Windows Server used as Load Generator. Each Window session automatically starts a Load Generator process which is automatically added to the list of available Load Generators for the zone.

For more information, see the Terminal Services tab from the Load Generator Zone settings.

NL-TerminalServices

For more information, see Terminal Services.

With custom scripts

If the NeoLoad Terminal Services feature cannot be used for any reason and a custom script is required, here is the command to start a Load Generator Agent in Terminal Services mode:

The Load Generator then uses a unique working folder and picks an available port dynamically. Add the Load Generator to NeoLoad by using the Bind action from the Terminal Service feature. For more information, see Terminal Services.

Screenshots on error

In the case you have troubles identifying the cause of a failure, you can select the Show SAP GUI interface and take screenshots on error option when running the test. You can see the screenshots in the detail of the error listed in the Errors tab of NeoLoad.

NL-SAPTestGuide-Screenshotonerror

It is recommended to select this option only for debugging purposes as it consumes a large amount of graphical resources and may return unreliable response times and raises additional errors in case of an overloaded Load Generator. You may need to decrease the load in such mode. For more information, see Runtime errors.

FAQ

The SAP GUI client executable is not properly detected, can I specify the path?

In the case NeoLoad does not detect the path of SAP GUI or does not pick the appropriate version, see Modify the path to the SAP GUI client.

Why do I get error “Scripting support is disabled by the user” with SAP Logon?

Scripting must be enabled on all SAP GUI installations. For more information, see Enable SAP GUI scripting.

What is the SAP GUI component coverage by NeoLoad?

For more information, see the mapping table.

Can I convert my LoadRunner SAP GUI scripts to a NeoLoad project?

Yes, the NeoLoad Script Converter supports ‘Web - HTTP/HTML’ and ‘SAP GUI’ protocols. As LoadRunner’s API to handle SAP GUI is close to the SAP scripting API, the mapping table can help you in the conversion process.