Tests can be created using test clips that were either automatically or manually created. In general, HTTP(S) Message Recording is the preferred method for test clips based on messages, while browser recording is the preferred method for creating Web UI tests.
Automatic HTTP(S) Test Clip Creation
You can create a new HTTP(S) test clip automatically from within the Clip Editor (newer method) or by creating a recording in the Recording Editor and converting it (older method). Using the newer method in the Clip Editor will also create your background recording (where it can be found in the Recordings list). Refer to HTTP Recording into the Clip Editor.
Any existing HTTP or HTTPS recording can be used to create a clip. To convert a recording to a clip, open it from Central > HTTP(S) Message Recordings and follow the steps described in Converting a Recording to a Test Clip.
Manual Test Clip Creation
Before creating a new Test Clip manually you must have at least one Target and/or at least one Script in your Repository.
- A Target points to the application, service, or web site that you want to test, including its location (URL), and any authentication information necessary to successfully run a test.
You can verify that you have a target in Central > Targets.
Test clips can be created manually or automatically by using one of three recording techniques: HTTP(S) Recording, Browser Recording., or Mobile App Recording (also known as TouchTest Recording). In the automatic process, targets are automatically created as an output of the recording process.
If you want to create a Browser Action Test Clip, you should install the SOASTA Browser Recorder (Firefox only). Go to Central > Welcome. Under Download, click the link for Browser Recorder Installer. HTTPS recording and Browser Action test playback both require Installing SOASTA Conductor.