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.
Native JMeter Pressure Test
- When the JMeter test plan is debugged, save the JMX and CSV files.
- Prepare test resources and create a private resource group.
- Log in to the CodeArts PerfTest console, choose Resource Groups in the navigation pane, and click Create Resource Group.
- (Optional) If this is the first time you create a private resource group, grant CodeArts PerfTest permissions necessary for creating private resource groups.
- If you do not have a CCE cluster, perform 2.d to create one before creating a resource group. If a CCE cluster is available, go to 2.e to create a resource group.
- Create a cluster.
In the upper part of the page, click create one. The CCE console is displayed. For details about how to create a cluster, see Buying a CCE Cluster.
Click Next: Select Add-on. On the page displayed, select the add-ons to be installed during cluster creation.
Click Next: Add-on Configuration. Retain the default settings.
Click Next: Confirm configuration. After confirming that the cluster configuration is correct, select I have read and understood the preceding instructions and click Submit. It takes about 6 to 10 minutes to create a cluster.
After the cluster is created, return to the cluster management page and click Create Node. For details about how to create a node, see Creating a Node.
Click Next: Confirm. After confirming that the node configuration information is correct, select I have read and understood the preceding instructions and click Submit.
After the node is created, return to the CodeArts PerfTest console.
- Create a resource group.
Choose Resource Groups in the navigation pane, and click Create Private Resource Group.
Set the parameters listed in Table 1.Table 1 Creating a private resource group Parameter
Description
Resource Group Name
Name of the private resource group to be created.
Debugging Cluster
Select a CCE cluster from the drop-down list.
Debug Node
Select the management node that performs a pressure test.
The debugging node cannot be changed after the resource group is created.
Execution Node
Select a pressure target machine that provides performance data during a pressure test.
Click Create.
- Create a JMeter test project.
Go back to the CodeArts PerfTest console and choose JMeter Projects in the navigation pane. Click Create JMeter Project. Enter the project name and click OK.
- Import a JMX file.
- On the JMeter Projects page, click
to edit the test plan.
- On the test plan tab, click Add Task Plan.
- In the dialog box that is displayed, click Select File, select a JMX file, and click Upload. When the file is imported, the dialog box closes automatically and the Test Plan List tab is displayed. You can view the added test plan.
Figure 1 Importing a JMX file
- (Optional) On the test plan tab page, click Third Party Jar. In the displayed dialog box, click Import File, select and import the JAR package on which the test plan depends. After the package is imported, the dialog box closes.
Figure 2 Importing a JAR package
- On the JMeter Projects page, click
- (Optional) Import the variable file.
In the test plan list, click
and choose Variable File. In the displayed dialog box, click Local Import, select the variable file referenced by the test plan, and import the file. After the file is imported successfully, close the dialog box.
Figure 3 Importing variable file 1Figure 4 Importing variable file 2 - Edit a thread group.
Click the task name in the JMeter test plan list. The thread group list is displayed. After the editing is complete, click OK.
- Number of threads corresponds to Number of Threads in the local JMeter program.
- Warm-up Time corresponds to Ramp-up period in the local JMeter program.
- Number of Cycles indicates the number of cycles to be tested.
Figure 5 Editing a thread group - Debug the JMeter test task.
Click Debug, select the target test resource group as the executor, and click Start to start debugging. If an error was reported in the debugging result, edit the case based on the log information and debug it again.
Figure 6 Starting debugging - Execute the JMeter test task.
Click Start. In the dialog box that is displayed, specify Resource Group Type and Enterprise, and click Start to start the test task.Figure 7 Starting a test task
- View a test report.
After the test task is started, click View Report to view the monitoring data and chart report of each metric generated during the pressure test.
After the pressure test is complete, an offline test result report is generated automatically. You can download and view the report of the completed test task.
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