Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- 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
Show all
Copied.
Mapping Between JMeter and PerfTest Fields
CodeArts PerfTest supports the import and automatic switchover of the JMeter script. Table 1 describes the mapping between JMeter and PerfTest fields.
JMeter Field |
PerfTest Field |
Parameter Description |
|
---|---|---|---|
Thread group |
Name |
Transaction Name/Task Name |
The HTTP request and the subsequent HTTP request form a transaction. If no valid value is obtained, number of concurrent requests is 1 and the duration is 1 minute by default. |
Number of threads |
Number of concurrent test tasks |
||
Duration |
Test task duration |
||
User-defined variables |
Name |
Enumeration variable name |
Global variable, enumerated type. The name must be unique. |
Value |
Enumeration variable value |
||
User parameters |
Name |
Enumeration variable name |
Global variable, enumerated type. The name must be unique. |
User_1 |
Enumeration variable value |
||
User_2 |
Enumeration variable value |
||
... |
Enumeration variable value |
||
User_N |
Enumeration variable value |
||
HTTP header manager |
Name |
Packet header |
When the POST, PATCH, PUT, or DELETE request mode does not contain the Content-Type header, the Content-Type header value is set to application/x-www-form-urlencoded by default. |
Value |
Header value |
||
Default HTTP request |
Protocol |
- |
If the HTTP request does not contain a value, the default value of the HTTP request is used. Priority: HTTP request > thread group > test plan. |
Server name or IP address |
|||
Port number |
|||
Path |
|||
Parameter |
|||
Message body data |
|||
Response timeout in the advanced options. |
|||
HTTP request |
Protocol |
Protocol type |
Packet. Ignore request modes except POST, GET, PATCH, PUT, and DELETE. The default value is 5,000 ms when no response timeout value is obtained. |
Protocol, server name or IP address, port number, and path |
Request URL |
||
Method |
Request mode |
||
Parameter |
Add the content to the URL or packet content as required. |
||
Message body data |
Packet content |
||
Response timeout in the advanced options. |
Response timeout |
||
Regular expression extractor (the response field to be checked) |
Body |
Packet content |
Response extraction. Only the regular expression extractor and fixed timer under the HTTP requests can be imported. If the default value is empty, the reference name is used by default. |
Body (unescaped) |
Packet content |
||
Body as a Document |
Packet content |
||
Message header |
Header |
||
URL |
URL |
||
Response code |
Response code |
||
Request Headers. Response information. |
Import is not supported. The regular expression extractor is ignored. |
||
Regular expression extractor |
Reference name |
Variable name |
|
Regular expression |
Regular expression |
||
Template |
Sequence number of matching item |
||
Match digits |
Expression value |
||
Default value |
Default value |
||
Fixed timer |
Thread latency |
Duration |
Think time. If no valid value is read, the default value 1,000 is used. |
Random function |
- |
Random number in a range |
An integer generated randomly within the range entered by a user. For example, ${__Random(-2147483648,2147483647)} |
JSON extractor |
Name of created variables |
Variable name |
Response extraction. Default extraction range: parameter values in .json format. Only the JSON extractor under the HTTP requests can be imported. |
JSON Path expressions |
Key name |
||
Default Values |
Default value |
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