- 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.
Introduction
CodeArts PerfTest provides performance test services for cloud applications that are built based on HTTP, HTTPS, TCP, UDP, HLS, RTMP, WebSocket, MQTT, or HTTP-FLV. CodeArts PerfTest quickly simulates service peaks with a large number of concurrent users. It allows you to define the contents and time sequences of packets and supports complex combinations of multiple transactions. After tests are complete, CodeArts PerfTest provides professional test reports to evaluate your service quality.
You can complete a performance test in four steps listed as in the following figure.

You can quickly get familiar with the CodeArts PerfTest usage through the interactive walkthroughs.
Basic Concepts
- Test Project: Test projects are classified into PerfTest projects and JMeter projects. PerfTest projects provide project management capabilities, allowing you to share and reuse the contents of transactions, pressure test tasks, and test reports within a test project, and create different test projects for different test programs. JMeter projects are used to import JMeter scripts to CodeArts PerfTest.
- Transaction: A transaction is a user-defined operation model that consists of HTTP/HTTPS/TCP/UDP/WebSocket packet, think time, response extraction, checkpoint, and HLS/RTMP/HTTP-FLV/MQTT packet.
- Packet: Packets are data blocks transmitted between applications such as HTTP. These data blocks start with text metadata that describes the packet content and meaning. The text metadata is followed by optional data. Packets are transmitted among clients, servers, and agents.
- Think Time: To better simulate user behavior, insert a waiting time between different operations. For example, when a user receives data from the server, the user may wait several seconds before viewing data and providing responses. This period of time is called think time.
- Response Extraction: If a transaction contains multiple packets, the output of the previous packet, which is extracted by a regular expression or JSON, is used as the input of the next packet.
- Checkpoint: Checkpoints are where you define the verification information to determine whether the contents returned by the server are correct.
- Number of Concurrent Users: It refers to the number of users performing operations on a system at the same time. In CodeArts PerfTest, it is the number of virtual users you define when you configure a test phase.
- Response Time: Response time indicates the duration from the time when a client sends a request to the time when the client receives a response from the server.
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