หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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 Crontask
Prerequisites
A PerfTest or JMeter project has been created, and test tasks are included.
Procedure
- Log in to the CodeArts PerfTest console. In the navigation pane, choose Scheduled Test. Then click Create.
- Set the basic information by referring to Table 1.
Table 1 Creating a crontask Parameter
Description
Related Project
Select an existing PerfTest or JMeter project.
Related Task
Select the task for which you want to perform a scheduled pressure test.
A task can be associated with only one scheduled pressure test task to be executed.
Crontask Name
Name of the crontask
Description
Description of the crontask
Resource Group
Select a test resource group for the crontask.
- You can select a shared resource group or an existing private resource group for a PerfTest project. Shared resource groups of a user can be bound to only one pressure test task.
- Only existing private resource groups can be selected for a JMeter test project.
Enterprise Project
Select the corresponding enterprise project.
This option is unavailable for personal accounts.
Run Frequency
Frequency of running the crontask. Option: Run only once and Run regularly.
- Run only once: The task is executed only once at the time set in Date of running.
- Run regularly: The period settings can be Monthly, Weekly, and Advanced.
- Monthly: The task is executed every month on the specified running date (one day or multiple days) and time.
- Weekly: The task is executed every week on the specified running date (one day or multiple days) and time.
- Advanced: The task is repeatedly executed based on crontab expressions. Use this mode if you are familiar with crontab expressions.
The rules for entering running dates are as follows:
Minute: integers ranging from 0 to 59, and operators * , - /
Hour: integers ranging from 0 to 23, and operators * , - /
Day (days in a month): integers ranging from 1 to 31, and the operator ? * , - /
Month: Only * (monthly) is supported.
Week (days in a week): any days in a week and the question mark (?) operator
The day and week rules are mutually exclusive. When a non-default value is set for one parameter, the default value ? is automatically set for the other parameter.
Deadline
Set this parameter only when Run Frequency is set to Run regularly.
The task will not be executed after the deadline. The furthest deadline is one year later.
- When the configuration is complete, click Sure.
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