Help Center/ CodeArts PerfTest/ Getting Started/ Introduction
Updated on 2024-10-21 GMT+08:00
View PDF
Share

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.

Figure 1 Performance test procedure

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.