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 Transaction
A transaction refers to a complete operation process from end to end, such as a login, criteria-based query, and payment. A transaction can be used by multiple test cases. CodeArts PerfTest supports flexible combination of transactions. You can create multiple transactions to a test project.
Prerequisites
A test project has been created. For details on how to create a test project, see Creating a Test Project.
Procedure
- Log in to the CodeArts PerfTest console and choose PerfTest Projects in the left navigation pane.
- Locate a PerfTest project to be edited and click
to edit the transaction library.
- On the Transaction Library tab page, click create a transaction, configure the following parameters, and click OK.
- Transaction Name: name of a customized transaction.
- Type: Normal transaction refers to transactions of performance tests in normal scenarios, including API tests of applications built based on HTTP/HTTPS/TCP/UDP/HLS/RTMP/WebSocket/HTTP-FLV/MQTT protocols. Multiple transaction requests can be connected with each other.
- Add requests to the transaction and click OK.
When the transaction type is Normal, you can add four types of request compositions: packet, think time, response extraction, and checkpoint. Packet is mandatory.
- Packet: data blocks transmitted between HTTP-based applications. For details, see Adding Request Information (Packet).
- Think Time: time interval between two actions. For details, see Adding Request Information (Think Time).
- Response Extraction: If multiple packets exist in the same transaction, use regular expressions or JSON to extract the output of the previous packet for the input of the next packet. For details, see Adding Request Information (Response Extraction).
- Checkpoint: used to verify if contents returned by servers are correct through customized verification information. For details, see Adding Request Information (Checkpoint).
- (Optional) A transaction contains one or more requests. If your transaction contains multiple requests, click Add Request to add more requests. Up to 40 requests can be added to a normal transaction.
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