このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- CodeArts PerfTest Use Process
- Permissions Management
- Test Resource Management
- PerfTest Project Management
-
PerfTest Case Management
- Test Case Description
- Directory Management of Test Cases
- Creating a Test Case
-
Configuring a Test Case (High-Performance Test Projects)
- Filling in Case Details
- Configuring a Case Script
- Adding Request Information (Packet)
- Adding Request Information (Think Time)
- Adding Request Information (Response Extraction)
- Adding Request Information (Checkpoint)
- Adding a Data Instruction, Cycle Controller, Condition Judgment, or Rendezvous Point
- Adding Concurrency Weight Controllers and Throughput Controllers
- Pressure Configuration
- Advanced Configuration
- SLA Configuration
- Configuring a Test Case (Scalable Test Projects)
- Setting Global Variables (High-Performance Test Projects)
- Setting Global Variables (Scalable Test Projects)
- Binding a Domain Name
- Plug-in Management
- Resetting Configurations
- Managing Test Cases
- Debugging a Case
- Batch Operations
- PerfTest Task Management
- PerfTest Report Management
- Transaction Management
- JMeter Test Project Management
- Crontask
- Configuring SLAs
- Auditing
- Reference
- Best Practices
- API Reference
- SDK Reference
-
FAQs
- Resource Group Management
-
Pressure Test Project Management
- What Are the Differences Between Think Time and Duration in CodeArts PerfTest?
- What Is the Number of Concurrent Users?
- How Do I Fill in Packets?
- Why Does Transaction Debugging Frequently Fail?
- Which Headers Are Mandatory in an HTTP-based Packet Request?
- Why Is the CPU Usage of the Execution Node Used for the Pressure Test Constantly High?
- What Are the Differences Between Global Variables and Variables Extracted from Responses?
- What Is the Impact of the Bandwidth Applied for CodeArts PerfTest on Tests?
- What Are the Differences Between a JMeter Test Project and a PerfTest Project?
- How Do I Check If the Global Variable Values Are Read Sequentially in a Test Task?
- Pressure Test Report Management
-
General FAQs
- What Are the Permissions Required for Using CodeArts PerfTest?
- How Do I Use the New IAM Edition to Isolate Permissions by Enterprise Project?
- Does CodeArts PerfTest Support Windows Server 2016 Standard (64-bit)?
- What Can I Do If Chinese or Special Characters Are Not Properly Displayed When the API Response Body Containing Them Is Exported Using the Traffic Recording Plug-in?
-
Using JMeter Projects
- What Are the Differences Between the JMeter Engine of CodeArts PerfTest and the Open-source JMeter?
- What Scripts Does the JMeter Engine of CodeArts PerfTest Support?
- Which Operations in Scripts Are Not Supported by the JMeter Engine of CodeArts PerfTest?
- What Are the Possible Causes of a JMX File Import Error in a JMeter Test Project?
- What Are the Suggestions for Using CodeArts PerfTest Scripts?
- How Do I Use the Global Variable Function?
- What Should I Pay Attention to When Uploading a Third-Party JAR Package?
- What Should I Pay Attention to When Uploading a CSV File?
- What Should I Pay Attention to When Uploading a Custom Installation Package?
- Why Does CodeArts PerfTest Return Garbled Characters When Content-Type in the Request Header Is Set to UTF-8 in JMeter?
- What Are the Meanings of Log Errors in a JMeter Report?
- Why Does JMeter Case Debugging Fail in Less Than 5 Seconds and No Data Is Displayed on the Page?
- Videos
- General Reference
Copied.
Importing Recorded Scripts
In performance tests, virtual users simulate real users to use the tested system. The simulation process, such as login, search, and purchase in e-commerce applications, is implemented through recorded scripts. CodeArts PerfTest supports the record tool plug-in on the Chrome browser (version 26 or later versions). In the pressure test system, you can manually perform operations to capture request content and generate .json files. The recorded scripts simulate the actual operations of users, reducing the workload of manual packet writing and facilitating the use of the CodeArts PerfTest system.
Notes and Constraints
Downloading and Installing the Chrome Recording Plug-in
- Download the recording plug-in for Chrome.
- Decompress the installation package using a decompression tool.
- Enter chrome://extensions/ in the address bar. The extension page is displayed.
- Enable the developer mode on the extension page.
Figure 1 Enabling the developer mode
- Click Load unpacked and load the folder decompressed in 2.
- When the installation is complete, the icon of the recording tool
is displayed in Extensions in the upper right corner of the browser.
Figure 2 Recording tool
Recording Scripts
Use the CodeArts PerfTest recording tool to record scripts.
- Open Chrome and click the icon of the CodeArts PerfTest recording tool
in the upper right corner of the browser. The recording box is displayed.
- Click Start Recording.
- On the new tab page of the browser, enter the URL to be tested. The recording tool automatically records the HTTP requests during the access operation.
- When the recording is complete, switch to the recording tool page and click Pause Recording.
- By default, the record tool displays all types of requests. You can select the request composition based on the service requirements by clicking the Filter Content check box.
- other: others
- script: script
- xmlhttprequest: XML HTTP request
- main_frame: main frame
- stylesheet: style sheet
- image: image
- font: font file
- Ping: ping test
- If you select a request, the content of the request is displayed on the right of the page.
If the recorded content is not required or a new request needs to be recorded, perform the following steps to record scripts again:
- Click Clear Content to clear the recorded request content.
- Click Start Recording.
- Perform operations on the new tab page and record again.
- Click Export, select the request to be exported, and click Confirm Export. The Export Content dialog box is displayed. Click Generate .json File to save the file to the local host. Plug-in recording script. The body type does not support the payload format.
- Close the tab where the record tool is located to disable the record tool.
Importing Recorded Scripts
- Log in to the CodeArts PerfTest console and choose PerfTest Projects in the left navigation pane.
- Locate a PerfTest project to be edited and click
to edit the transaction library.
- Import a recorded script using either of the following methods:
Method 1: On the Transactions tab page, click Import Script. Set Script Type to Manual recording script. Select the transaction and recorded script file to be imported. The recorded script contains one or more packet requests and can be imported to the corresponding transaction mode.
Method 2: On the right of the desired transaction name, click Import Recorded Script and select the script file to be uploaded.
- Click Import. If the scripts are imported successfully, the system displays a message indicating this.
- Under the transaction, you can view the packets successfully imported. The number of packets successfully imported is the same as the number of requests in the uploaded script file.
- (Optional) Click
to modify the imported scripts by referring to Adding Request Information (Think Time) based on service requirements.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot