Integrating Silk Test Workbench into SAP eCATT
If you need to test products that are based on the HTML technology, you can integrate Silk Test Workbench as an external tool into SAP eCATT (eCATT). You can then use Silk Test Workbench from within eCATT to record, playback, debug, and edit test scripts.
Integrating Silk Test Workbench into eCATT presents the following advantages:
- You can store all Silk Test Workbench assets and eCATT tests in the same SAP/R3 database.
- You can view all eCATT and Silk Test Workbench test results in the same view in eCATT.
- You can share your tests with the other testers in the same SAP system.
- By passing parameters between eCATT and Silk Test Workbench, you can create truly integrated test scenarios.
- You can use data from SAP test data containers in Silk Test Workbench.
- In Silk Test Workbench, you can pass parameters between eCATT and Silk Test Workbench by using script arguments.
When you have finished integrating Silk Test Workbench and eCATT, you can work with Silk Test Workbench out of eCATT. You can then record, playback, debug, and edit visual tests and .NET scripts in Silk Test Workbench out of eCATT. You can also save Silk Test Workbench assets in a BLOB, load a BLOB from the SAP/R3 database, and manage test script arguments.
To be able to work with Silk Test Workbench out of eCATT, perform the following steps:
- Login to your SAP server as an administrator. You have to have administrator permissions to make your changes permanent.
- Enable scripting on the application server. For additional information, see the topic Enabling Scripting on the Application Server in the SAP Help.
- On your SAP server, register Silk Test Workbench in the ECCUST_ET table in eCATT.
- Call the SET_EXTERNAL_TOOL function module using the SE37 transaction.
- On the first screen, enter the function module name SET_EXTERNAL_TOOL.
- From the Function Module menu, select Test > Single Test.
- In the following window, enter the following parameter values:
Silk Test Workbench
Silk Test Workbench for eCATT
- Press the Execute button (F8). The ECCUST_ET table should now include Silk Test Workbench.
- For each client, enable scripting on the client front-end server.
Note: Clear the Notify when a script attaches to a running GUI check box to prevent a confirmation dialog box from displaying each time Silk Test Workbench records against an SAP application.
For additional information, see the topic Enabling Scripting at the Front End in the SAP Help.
- On your SAP server, create a new user account.
- In the transaction PFCG, type the role SAP_ECET, and select Change. You can ignore the warning that appears.
- Switch to the Authorizations tab and select Change Authorization Data.
- Place the cursor over the top node of the SAP_ECET tree and select Authorizations > Generate.
- Click Back to return to the role maintenance screen.
- Click Save.
- On the client machine on which you will be using Silk Test Workbench in combination with eCATT, install both Silk Test Workbench and the SAPGUI client.
- Select Silk Test Workbench as the external testing tool for eCATT. For additional information, see the topic Using an External Tool with eCATT in the SAP Help.
You can now execute visual tests and .NET scripts in Silk Test Workbench out of the eCATT UI.
To view a video that shows the integration of Silk Test Workbench with eCATT, view Borland Silk Test workbench and SAP e-catt integration.
Instead of starting Silk Test Workbench from eCATT, you could also start the standalone version of Silk Test Workbench and then use BLOBs to transfer data between Silk Test Workbench and eCATT. For additional information on this approach, refer to the Silk Test Workbench Help.