Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- 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.
Creating a Test Case
Procedure
- Log in to the CodeArts PerfTest console and choose PerfTest Projects in the navigation pane.
- Locate the row that contains the target PerfTest project, and click the test project name, for example, Web-test. The test project details page is displayed. On the Cases tab, you can view the default directory and sample cases that are automatically generated.
- In the default directory, choose Sample Case. Click Case Script and select Pre-Steps or Steps.
Pre-Steps are executed only once in each execution thread. This configuration is optional.
Steps are executor of a test case, which needs to be configured.
- In the case, click Add Request. Enter a request name and add requests.
- Packet
(Mandatory) Packets are data blocks sent between HTTP applications.
Click the Packet tab, and set packet parameters based on the actual service to be tested.
- Think time
(Optional) To better simulate user behavior, it is necessary to simulate the waiting time between different operations. For example, when you receive data from a server, you may wait for several seconds to view the data before responding. This latency is called Think Time.
Set Think Time based on requirements. For more effective testing, do not set a long think time. You are advised to test the server for the worst case scenario.
Enable Think Time and set Duration to 1000 ms.
- Response extraction
(Optional) If multiple packets exist in the same case, use regular expressions or JSON to extract the output of the previous packet for the input of the next packet.
Enable Response Extraction and set parameters.
- Checkpoint
(Optional) When enabled, you can check whether the content returned by a server is correct through customized verification information.
Enable Checkpoint and set parameters.
- Packet
- Select Pressure Stage.
You can select different pressure modes and add multiple phases. Each phase can simulate different numbers of concurrent users.
- Click Save.
- Click Debug in the upper right corner of the page. Select the target test resource group as the executor and click Start.
- Click View log to view the test case debugging details.
If an error was reported in the debugging result, edit the case based on the log information and debug it again.
- On the Debug log tab page, you can view the debugging history.
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