Skip to content

Creating and Opening Scripts

Recording a new script

Tell the assistant to record — for example:

  • Record a new script
  • Record http://www.example.com

If you did not include a URL, the assistant asks for one. It then opens a capture browser on that URL and recording begins. Perform your business flow in the browser exactly as a real user would — sign in, search, add to cart, check out.

When you are done, stop the recording by any of these methods:

  • tell the assistant — stop recording — or
  • press Stop in the Recorder; or
  • close the capture browser.

The recorded traffic becomes a WebLOAD script, which appears in the Recorder and in the chat's script panel. When you stop through chat, the assistant reports the captured request count. If you stop in the Recorder or close the browser, the assistant confirms the stop; you can then ask it to summarize the script and suggest next steps.

Recording a useful business flow

  • Start from a stable entry page and complete one recognizable journey, such as sign-in through checkout, rather than mixing unrelated tasks.
  • Wait for each business page to finish before moving on. Background polling, telemetry, and static assets may be captured, but they are not substitutes for the business requests the script must replay.
  • Use test accounts and test data approved by your organization. Recorded traffic can contain form values, headers, cookies, and session identifiers.
  • Finish the flow before stopping. Closing the capture browser is a stop action, not a pause that can be resumed later.

What to do after recording

  1. Save the Recorder project so local script history can identify it safely.
  2. Choose Replay and diagnose. A successful recording is not yet proof that the captured script can replay with a fresh session.
  3. Apply only the improvements supported by replay evidence, commonly correlation, parameterization, transactions, or response validations.
  4. Run Ready for a load test? after the script replays cleanly to identify remaining quality gaps.

Opening an existing script

To work on a script you already have:

  • Open an existing script — the assistant asks which project to open.
  • Open C:\Projects\checkout.wlp — opens a specific project directly.

Scripts open in the WebLOAD Recorder as usual; the assistant works on the project the Recorder has open.

Viewing and understanding the script

Ask at any time:

  • Show me the script
  • Analyze the current script
  • What URLs were recorded?
  • List the transactions and validations

These are read-only questions — the assistant inspects the script and answers without changing anything.

Editing the script

Ask for the change in plain language:

  • Add a 3 second sleep after the login request
  • Comment out line 12
  • Rename the transaction "Tx1" to "Login"

The assistant shows a proposal card with the exact change. The script is modified only after you approve, and an applied change can be reversed with undo.

The assistant can also make more advanced localized edits when you identify the target clearly, such as adding a request, branch, loop, log message, timer, counter, or supported request property. Generated code remains intended for the WebLOAD JavaScript 1.7 runtime, and every change still goes through review and approval.