Recording a socket API performance test

You can record a socket API test from any client program on your computer or from a Java™ client program in the workbench. When you record, the recording wizard automatically starts the client program and records all the data that transits through the socket API.

Before you begin

Tests are stored in performance test projects. If your workspace does not contain a performance test project, the test creation wizard creates one with a name that you can change. To store a test in a specific project, verify that the project exists before you record the test.

Ensure that you have a working client program and that you have network connectivity with the server.

Ensure that the session that you are recording is reproducible. This means that when the recorded actions are replayed by the test, the same responses from the server will be received.

Procedure

To record a socket test:

  1. In the Performance Test perspective, click the New Test from Recording buttonNew Test from Recording toolbar button or click File > New > Test from Recording.
  2. In the New Test from Recording wizard, click Create a test from a new recording, select Socket Test, and click Next.
  3. On the Select Location page, select the project and folder where you want to create the new test, type a name for the test, and click Next. If necessary, click Create Parent Folder buttonCreate Parent Folder to create a new project or folder
  4. On the Select Client Application page, select the type of client program that you want to use to record the test:
    • To specify any client program located on your computer, select Managed Application and click Next.

      On the Managed Application Options page, click Browse to specify the Program path. If necessary, specify the Working directory, and type any command line Arguments required by the program.

      If the program requires user input from a command line interface, select Open console for user input.

    • To record a TN3270 terminal emulation session, select IBM Personal Communication or Attachmate EXTRA! X-treme, and click Next.

      If required, specify a session file to launch the TN3270 session.

      Note: Using this method to record a TN3270 session will produce a socket API performance test based on the TN3270 protocol traffic. To record a TN3270 test, refer to Recording a TN3270 performance test.
    • To record an HTTP session, select Microsoft Internet Explorer or Mozilla Firefox, and click Next.

      If you choose Mozilla Firefox, you can specify Firefox profile

      Note: Using this method to record an HTTP session will produce a socket API performance test based on the HTTP traffic. To record an HTTP test, refer to Recording an HTTP test.
  5. If this is the first time you record a socket API performance test, read the Privacy Warning, and select Accept to proceed.
  6. Click Finish to start recording. A progress window opens while the client program starts.
  7. Use the client program to perform the actions that you want to test. You can use the Recorder Test Annotations toolbar to add comments, record synchronizations, or take screen captures during the recording.
    • To add a comment to the recorded test, click the Insert comment icon Insert comment button.
    • To add a screen capture to the recorded test, click the Capture screen icon Capture screen button. Screen and window captures make your tests easier to read and help you visualize the recorded test. You can change the settings for screen captures and add a comment to the image.
    • To manually add a test synchronization to the recording, click the Insert synchronization icon Insert synchronization button.
    • To manually add a transaction folder to the recording, click the Start Transaction button Start Transaction and Stop Transaction button Stop Transaction buttons to start and stop the transaction.
    • To insert a split point into the recorded test, click the Split point icon Split point button. Split points allow you to generate multiple tests from a single recording, that you can replay in a different order with a schedule.
  8. When you have finished test actions in the program, stop the recorder. You can do this by closing the client program or by clicking the Stop Stop icon button in the Recorder Control view. A progress window opens while the test is generated. On completion, the Recorder Control view displays the message Test generation completed, the Test Navigator lists your test, and the test opens in the test editor.