Metric Configuration

By standardizing global benchmarks for functional/performance/stability test metrics, 90% of testing scenarios can be evaluated uniformly while allowing interface-level flexibility. Once configured, settings automatically apply to all new test tasks, significantly improving testing efficiency.

⚠️ Key Notes:

1. Current metric configurations serve as default global settings, effective for all projects.
2. Interface-level configurations override global settings. Configuration path: API → Target API → Metric Configuration

I. Functional Test Metrics Configuration

Defines baseline pass criteria for smoke tests and security tests

1. Smoke Test Configuration

Purpose: Verify basic API availability

Steps:

1. Navigate to Configuration Center → Metric Management → Functional Metrics and click "Edit"
2. Toggle on Smoke Test Cases
3. Select detection strategies (default: "API Availability"):
   • ☑️ Service Responsiveness: Non-5xx status codes
   • ☑️ API Availability: 2xx status codes (recommended)
   • ☑️ Custom Rules: Script-based evaluation
     

2. Security Test Configuration

Purpose: Prevent unauthorized access
Steps:

1. On the same page → Toggle on Security Test Cases
2. Select validation logic:
   • ✅ Positive Validation: Exclude 401/403 statuses (default)
   • ✅ Negative Validation: Require 401/403
   • ✅ Custom Policy: Script-based authorization logic
     
3. Click "Save"

II. Performance Test Metrics Configuration

Sets core thresholds for stress testing

1. Core Parameter Matrix

Metric	Default	Business Impact	Optimization Suggestion
Concurrent Users	500	System capacity limit	Set at 120% of production traffic
90% Response Time	≤500ms	User experience	≤200ms recommended for internet services
Error Rate	≤0.01%	Business reliability	Set to 0% for payment systems
Ramp-up Step	50 users	Test precision	10% concurrency increase per step

2. Configuration Steps

1. Navigate to Metrics → Performance Metrics and click "Edit"
   
2. Modify key parameters
3. Click "Save"

⚠️ Financial Systems Note:

• Error rate must be set to 0%
• Achieve via global or interface-level configuration
• Recommended ramp-up step: 10 (precision-first)

III. Stability Test Metrics Configuration

Verifies long-term system reliability standards

1. Core Parameter Matrix

Metric	Default	Business Impact	Optimization Suggestion
Concurrent Users	200	Steady load	Set at 70% of production traffic
Test Duration	30m	Stability window	24 hours recommended
90% Response Time	≤500ms	User experience	≤200ms recommended for internet services
Error Rate	≤0.01%	Business reliability	Set to 0% for payment systems

2. Configuration Steps

1. Navigate to Metric Management → Stability Metrics and click "Edit"
   
2. Business Layer Configuration:
   • Concurrent Users: 200
   • Duration: 30 minutes
   • Error Rate: ≤0.01%
3. Resource Layer (Optional):

   Resource	Threshold	Notes
   CPU	≤75%	Triggers alerts when exceeded
   Memory	≤75%	Critical for JVM applications
   Disk	≤75%	Key metric for logging systems
   Network	≤75MB/s	Core metric for video systems

4. Click "Save"

⚠️ Prerequisite for Resource Monitoring:
Complete Configuration → Nodes setup first

IV. Efficiency Metric Grading System

Quantifies team productivity with scoring standards

1. Five-Dimensional Evaluation Matrix

Tier	Workload	Completion Rate≤	Overdue Rate≤	Pass Rate≥	Savings Rate≥
Poor	100	35%	35%	30%	0%
Weak	100	50%	25%	45%	0%
Medium	100	65%	15%	60%	10%
Good	100	90%	5%	85%	20%
Excellent	100	100%	2%	90%	30%

2. Applications

• Efficiency Dashboard: Auto-generates team heatmaps
• Sprint Retrospectives: Identifies bottlenecks
• Performance Reviews: Objectively quantifies output