Recording a session is an easy task.
▪First, you compile your server with ServerModule->Options->soAllowSessionRecording = True. This parameter must be set to False once your app is ready for production.
▪Build and run your uniGUI server.
▪In Stress Test Tool set Url to Web Application to Url address of your server. If your server is running in the same machine, a typical address would be http://127.0.0.1:8077
▪Press the Record 
button. This will launch a new browser window which will show the main form of your web application. This action will use your system default web browser.
Session Recoding
▪At this stage you can start using the web application by navigating in menus, forms, grids, etc. All of your actions will be recorded.
▪You can continue recording this session until you think the coverage of the menus, forms, grids and functions of your app is enough.
▪When you are done, you can terminate your web application.
▪Now switch to Stress Test Tool and press the Stop button 
.
▪This finish your recording session and adds it to the list of available records for this project.
▪You can save your project using the Save button 
.
Important: To use a recorded session for the Stress Test Tool, it should be repeatable. In other words, all the recorded actions should always produce the same HTML content. For example, pressing Button1 should always open Form1 and selecting menu item User1 should always show a frame named TUserFrame. Normally, it is the case for 99% of the web applications where each user action results in the same output. There are certain user actions which may not produce a predictable result. Inserting rows in a DBGrid is an example. When the user inserts a new row, it creates a new grid row and also a new grid page (after inserting a certain number of rows). Hence, this action can produce a different JavaScript content which is not predictable and is dependent on the current number of rows in the attached database table. Because of this, it is recommended to avoid inserting data into a DBGrid while recording a session. Likewise, deleting or editing a row may not run properly during session playback. Consider that your table contains 100 rows and you delete a single row while recording. When you playback 100 instances of the same session, all of them will try to delete the same row while only one session can delete it.