AngusTester Resource Quota Management

AngusTester's resource quota system provides tenants with a comprehensive resource management mechanism to ensure stable system operation. Below are detailed descriptions of various resource quotas:

Quota Overview

Resource Type	Initial Quota	Maximum Allowable Value	Adjustable in Private Deployment	Adjustable in Cloud
Project Management
Number of Projects	2,000	1,000,000	✅	✅
Number of Modules	5,000	1,000,000	✅	✅
Number of Tags	5,000	1,000,000	✅	✅
API Management
Number of APIs	20,000	1,000,000	✅	✅
Number of Services	2,000	1,000,000	✅	✅
APIs per Service	1,000	2,000	✅	✅
Scenario Management
Number of Scenarios	20,000	1,000,000	✅	✅
APIs per Scenario	100	2,000	✅	✅
Mock Services
Number of Mock Services	100	1,000,000	✅	✅
Mock API Responses	50	2,000	✅	✅
Mock Data Iterations	5,000,000	5,000,000,000	✅	✅
Variable Management
Number of Variables	20,000	1,000,000	✅	✅
Variables per Entity	200	2,000	✅	✅
Execution Management
Number of Scripts	100,000	10,000,000	✅	✅
Number of Executions	100,000	10,000,000	✅	✅
Number of Reports	100,000	10,000,000	✅	✅
Task Management
Number of Tasks	200,000	50,000,000	✅	✅
Task Iterations	2,000	1,000,000	✅	✅
Performance Resources
Number of Nodes	1 (Private)/0 (Cloud)	1,000	❌	❌
Concurrent Users	1 (Private)/0 (Cloud)	2,000,000	❌	❌
Concurrent Tasks	1 (Private)/0 (Cloud)	1,000	❌	❌

Resource Details

📂 Project Management

• Number of Projects: Maximum number of projects that can be created
  Purpose: Controls system complexity and prevents excessive resource allocation

• Number of Modules: Number of functional modules per project
  Purpose: Manages the granularity of project subdivisions

📡 API Management

• Number of APIs: Total number of APIs that can be managed in the system
  Purpose: Controls the scale of API assets

• APIs per Service: Maximum number of APIs that can be associated with a single service
  Purpose: Ensures reasonable service decomposition

🎭 Scenario Management

• Number of Scenarios: Number of complex test scenarios
  Purpose: Manages resources for business flow testing

• APIs per Scenario: Maximum number of APIs that can be called in a single scenario
  Purpose: Prevents overly complex scenario designs

🎨 Mock Services

• Number of Mock Services: Number of Mock service instances
  Purpose: Controls resource consumption in simulated environments

• Mock Data Iterations: Maximum usage count for Mock data
  Purpose: Prevents infinite loops from consuming resources

🧩 Variable Management

• Number of Variables: Total number of global variables in the system
  Purpose: Centralizes the management of parameterized data

• Variables per Entity: Maximum number of variables that can be used by a single API/scenario
  Purpose: Avoids overly complex data dependencies

⚙️ Execution Management

• Number of Scripts: Total number of test scripts that can be stored
  Purpose: Manages the scale of script assets

• Number of Executions: Total number of historical execution records
  Purpose: Controls storage space usage

• Number of Reports: Total number of generated reports
  Purpose: Manages report storage resources

📅 Task Management

• Number of Tasks: Total number of test tasks
  Purpose: Controls the scale of automated tasks

• Task Iterations: Maximum number of runs for a single task
  Purpose: Limits the execution of looping tasks

🚀 Performance Resources

• Number of Nodes: Number of distributed test nodes
  Purpose: Controls cluster size
  Private Adjustment: Requires commercial authorization

• Concurrent Users: Maximum number of concurrent users
  Purpose: Ensures system performance stability
  Cloud Adjustment: Automatically scales based on demand

• Concurrent Tasks: Number of simultaneously running test tasks
  Purpose: Controls system load

Quota Adjustment Guide

Private Deployment Adjustments

1. Log in to AngusGM
2. Navigate to: System Management → Resource Quotas
3. Select the resource to adjust
4. Enter the new quota value (must not exceed the licensed range)
5. Save to apply

Cloud Service Adjustments

1. Access the cloud service management console
2. Submit a quota adjustment ticket
3. Describe the business expansion requirements
4. Wait for platform review and adjustment
5. Changes will take effect in the next billing cycle

Important Notes:

The number of nodes, concurrent users, and concurrent tasks cannot be directly modified in private deployments—a higher-spec license file must be reauthorized.
Performance resources in the cloud version are automatically adjusted based on demand without manual intervention.