This is the second Part of SAP Tutorial..
1 Click SilkPerformer’s Outline Project button to create a new project
2Enter a Project name and Project description.
3Select ERP/CRM\SAP\SAPGUI as the Application type.
4Click OK.
![]( "sap tutorial")
5Click the Model Script button on the Workflow Bar.
6If not selected already, select the Record radio button to record an application session.
7The SAPGUI Application Profile is preselected. If SAPGUI does not appear in the Application profile field, you do not have a SAPGUI client installed on your computer.
Note If you do not have a SAPGUI client installed, install SAPGUI Client 620 or 640 with the latest patch levels before creating a new SilkPerformer project.
If SAPGUI is still not listed in the Application profile field, you need to create the application profile for saplogon.exe. In SilkPerformer, open the System Settings dialog and select the Recorder icon on the left. Under the Application Profiles tab, add a new Application profile called SAPGUI and specify your saplogon.exe as executable in the Application path field. Specify Custom Application for the Application type and check the SAPGUI protocol checkbox. Click the OK button to confirm your settings and close the System Settings dialog.
8Click OK to launch saplogon.exe.
![]( "saplogon")
9Specify the SAP application server that is to be tested (this tutorial illustrates the testing of a SAP calendar application).
![]( "sap-tutoria")
Note On multi-lingual SAP systems it is recommended that you specify the language that is to be used by the SAPGUI client before recording begins. This prevents possible language differences between recording and replay (i.e., different languages may be selected by different load test agents, which will lead to Window Title Verification errors). This change can be made on the Properties dialog of each SAP connection in the SAPGUI login application. Edit the properties of each connection and click the Advanced button.
![]( "4")
On the Advanced Options dialog, deselect Default codepage and select your preferred language. Click OK to accept the change.
![]( "5")
10 Now simulate the actions of a typical user transaction. Login with username and password. Hit Enter
![]( "6")
11 Expand the tree and double-click the Owner item.
![]( "7")
12 Right-click a time frame and select Create Appointment from the context menu to create a new appointment.
![]( "8")
13 Define the appointment by setting Title, Appointment Type, Time, and Priority. Then click Save.
![]( "9")
14 Now edit the appointment you created by double-clicking it.
![]( "10")
15 Click the Delete button (trash can icon) to delete the appointment. A confirmation dialog appears. Click Yes to confirm deletion of the appointment.
![]( "11")
16 Click Exit (the yellow circular button) to exit the calendar application.
![]( "12")
17 Click Exit again to exit SAP Workbench. On the following confirmation dialog, confirm that you wish to exit the application.
![]( "13")
18 Close the SAPLogon application. This ends your simulated usertransaction.
19 Stop SilkPerformer‘s Recorder.
20 Save the recorded script file.
Note If no script has been recorded, review section “Client/ServerRequirements”.
Notice three things in the generated BDL script:
![]( "14")
SAP Tutorial Part-2:
Generating Test Scripts:
Procedure To generate a test script by recording a SAPGUI application session:1 Click SilkPerformer’s Outline Project button to create a new project
2Enter a Project name and Project description.
3Select ERP/CRM\SAP\SAPGUI as the Application type.
4Click OK.
5Click the Model Script button on the Workflow Bar.
6If not selected already, select the Record radio button to record an application session.
7The SAPGUI Application Profile is preselected. If SAPGUI does not appear in the Application profile field, you do not have a SAPGUI client installed on your computer.
Note If you do not have a SAPGUI client installed, install SAPGUI Client 620 or 640 with the latest patch levels before creating a new SilkPerformer project.
If SAPGUI is still not listed in the Application profile field, you need to create the application profile for saplogon.exe. In SilkPerformer, open the System Settings dialog and select the Recorder icon on the left. Under the Application Profiles tab, add a new Application profile called SAPGUI and specify your saplogon.exe as executable in the Application path field. Specify Custom Application for the Application type and check the SAPGUI protocol checkbox. Click the OK button to confirm your settings and close the System Settings dialog.
8Click OK to launch saplogon.exe.
9Specify the SAP application server that is to be tested (this tutorial illustrates the testing of a SAP calendar application).
Note On multi-lingual SAP systems it is recommended that you specify the language that is to be used by the SAPGUI client before recording begins. This prevents possible language differences between recording and replay (i.e., different languages may be selected by different load test agents, which will lead to Window Title Verification errors). This change can be made on the Properties dialog of each SAP connection in the SAPGUI login application. Edit the properties of each connection and click the Advanced button.
On the Advanced Options dialog, deselect Default codepage and select your preferred language. Click OK to accept the change.
10 Now simulate the actions of a typical user transaction. Login with username and password. Hit Enter
11 Expand the tree and double-click the Owner item.
12 Right-click a time frame and select Create Appointment from the context menu to create a new appointment.
13 Define the appointment by setting Title, Appointment Type, Time, and Priority. Then click Save.
14 Now edit the appointment you created by double-clicking it.
15 Click the Delete button (trash can icon) to delete the appointment. A confirmation dialog appears. Click Yes to confirm deletion of the appointment.
16 Click Exit (the yellow circular button) to exit the calendar application.
17 Click Exit again to exit SAP Workbench. On the following confirmation dialog, confirm that you wish to exit the application.
18 Close the SAPLogon application. This ends your simulated usertransaction.
19 Stop SilkPerformer‘s Recorder.
20 Save the recorded script file.
Note If no script has been recorded, review section “Client/ServerRequirements”.
Notice three things in the generated BDL script:
• The connection is opened with the full connection string.
• During replay new active windows are verified based on their titles.
• The login string must be customized with a parameter because the password value wasn’t retrieved during
