AngusTester Test Type Definitions

AngusTester provides business-focused testing solutions through specialized test type systems, core metric models, and scenario orchestration capabilities, empowering R&D teams to efficiently ensure system reliability and performance.

Test Type Overview

AngusTester offers four professional test types covering different quality verification needs:

Test Type	Core Objective	Key Features	Typical Scenarios
Functional Test	Verify basic business logic	Single user execution, rapid feedback	Smoke test · Script validation · Environment check · Change regression
Performance Test	Evaluate system concurrency	Progressive load increase, multi-dimensional observation	Bottleneck identification · Capacity planning · Optimization validation · Peak pressure simulation
Stability Test	Ensure long-term reliability	Constant load, continuous monitoring	Memory leak detection · Resource monitoring · Production stability validation · SLA compliance check
Custom Test	Meet specific validation needs	Full parameter flexibility	Hybrid scenario testing · Ad-hoc validation · Pre-production check · Special business models

View Full Documentation

Parameter Configuration Model

Basic Parameter Specifications

Test Type	Concurrency	Test Duration	Load Strategy
Functional Test	1 thread	Seconds (auto-adapted)	No load increase
Performance Test	100-5000 threads	5-120 min (default 50min)	Step increase (+100/min)
Stability Test	Baseline 200 threads (adjustable)	5-120 min (default 30min)	No load increase
Custom Test	User-defined	User-defined	User-defined

Scenario Application Guide

• Functional Test
  ▸ Script logic validation ▸ Environment health check ▸ Rapid regression testing ▸ Interface contract verification
• Performance Test
  ▸ System capacity baseline establishment ▸ Elastic scaling validation ▸ Performance optimization evaluation ▸ High-concurrency scenario simulation
• Stability Test
  ▸ Resource leak detection ▸ Long-duration operation validation ▸ Error rate fluctuation monitoring ▸ Production environment stability pre-check
• Custom Test
  ▸ Composite business scenario modeling ▸ Special traffic pattern simulation ▸ Canary release validation ▸ Fault injection testing

Core Metric System

Basic Execution Metrics

Metric	Description	Business Value
Concurrency (Threads)	Number of simulated concurrent users	Realistic load level simulation
Iterations	Number of test case executions	Functional coverage validation
Duration	Total test execution time (max=24h)	Stability validation core parameter
RampUp	Pressure increase step	System elasticity observation

View Full Documentation

System Performance Metrics

Metric	Description	Key Value
TPS	Transactions per second	Core measure of system throughput
ART	Average Response Time	Direct user experience metric
ErrorRate	Percentage of failed requests	Key system reliability metric
P99 Latency	99th percentile response time	High-assurance SLA validation basis

View Full Documentation

Resource Monitoring Metrics

Metric	Description	Monitoring Requirement
CPU Usage	Processor resource utilization
Memory Usage	Memory resource consumption
Disk Usage	Storage I/O resource usage
Network Usage	Network bandwidth utilization

View Full Documentation

Type-Metric Mapping Model

Dimension	Functional Test	Performance Test	Stability Test
Concurrency Model	Single user	Step increase (100-5000)	Constant load (200 threads)
Execution Duration	<30 seconds	50 minutes	30 minutes
Performance Target	-	TPS≥500, ART≤500ms	TPS≥500, ART≤500ms
Reliability Requirement	-	ErrorRate≤0.01%	ErrorRate≤0.01%
Resource Threshold	-	Resource usage≤75%	Resource usage≤75%

Model Interpretation

• Functional Test
  Single-user execution mode, supports ≤100 iteration validations
• Performance Test
  100 threads starting point, +100 threads/min step increase strategy, verifying system's peak capacity under TPS≥500 and P90 latency≤500ms conditions
• Stability Test
  Constant 200-thread load for 30 minutes, validating error rate and resource stability while meeting performance targets

Advanced Scenario Orchestration

Controller Component Library

Controller	Function Description	Key Parameters
Start Transaction Controller (TRANS_START)	Logical transaction grouping	Start marker
End Transaction Controller (TRANS_END)	Logical transaction grouping	End marker
Wait Controller (WAIT)	Simulate user operation intervals	Fixed/random wait time
Rendezvous Point (RENDEZVOUS)	Simulate traffic surge scenarios	Gathering users/timeout threshold
Throughput Controller (THROUGHPUT)	Traffic shaping control	TPS limit/smoothing factor

View Full Documentation

Orchestration Specifications

1. Transaction Control
   ▸ Use TRANS_START and TRANS_END to define transaction boundaries
   ▸ Mark transaction as failed if any request within it fails
   ▸ Transaction nesting prohibited

2. Traffic Control
   ▸ Throughput controller must set timeout threshold (recommended ≥5s)
   ▸ Rendezvous point scale ≤30% of max concurrency

3. Wait Strategy
   ▸ Must insert wait controller between key business steps
   ▸ Recommended: Gaussian distribution random wait (mean 1.5s±0.5s)

Best Practices

Efficiency Enhancement Guide

1. Performance Test Strategy
   ▸ Adopt step increase + plateau combination: 20% step increase → sustain 80% peak pressure
   ▸ Maintain 5-minute observation period after each increase

2. Stability Validation
   ▸ Execution duration ≥ 2 × business peak period
   ▸ Memory monitoring frequency ≤ 30s/sample

3. Scenario Design
   ▸ Limit transaction steps to 3-8 operations
   ▸ Performance-critical transactions ≥60% in hybrid scenarios

4. Monitoring Deployment
   ▸ Resource monitoring covers all core middleware nodes
   ▸ Enable real-time error log stream analysis

Start Your AngusTester Journey Now: 🔗 Enter AngusTester Console 🔗