Load Testing Configuration Generator

import http from 'k6/http';
import { check, sleep } from 'k6';
import { Rate } from 'k6/metrics';

export let options = {
  "scenarios": {
    "load": {
      "executor": "ramping-vus",
      "startVUs": 0,
      "stages": [
        {
          "duration": "30s",
          "target": 50
        },
        {
          "duration": "240s",
          "target": 50
        },
        {
          "duration": "30s",
          "target": 0
        }
      ],
      "gracefulRampDown": "30s"
    }
  },
  "thresholds": {
    "http_req_duration": [
      "p(95)<500"
    ],
    "http_req_failed": [
      "rate<0.1"
    ],
    "http_reqs": [
      "rate>10"
    ]
  }
};

const errorRate = new Rate('errors');

export default function() {
  const params = {
    headers: {
      'Content-Type': 'application/json',
      
      
    },
    timeout: '30s',
  };

  let response = http.get('https://api.example.com', params);
  
  
  check(response, {
    'status is 200': (r) => r.status === 200,
    'response time < 500ms': (r) => r.timings.duration < 500,
    'body contains data': (r) => r.body.length > 0,
  }) || errorRate.add(1);
  
  sleep(1);
}

export function handleSummary(data) {
  return {
    'summary.html': htmlReport(data),
    
    
  };
}

# Configuration Guide
# Load Testing Configuration Guide

## Test Configuration
- **Test Type**: Load
- **Framework**: K6
- **Target URL**: https://api.example.com
- **Duration**: 300 seconds (5 minutes)
- **Virtual Users**: 50
- **Ramp-up Time**: 30 seconds

## Setup Instructions

### Prerequisites
1. Install k6:
   - macOS: `brew install k6`
   - Linux: `sudo apt-get install k6`
   - Windows: `choco install k6`
   - Docker: `docker pull grafana/k6`

2. Save the generated configuration to appropriate files:
   - Save script as `test.js`

### Running the Test
```bash
k6 run test.js
# With options:
k6 run --vus 50 --duration 300s test.js
```

### Key Metrics to Monitor
- **Response Time**: P95 should be < 500ms for good user experience
- **Error Rate**: Should be < 1% for production systems
- **Throughput**: Requests per second handled by the system
- **Resource Utilization**: CPU, Memory, Network usage

### Test Types Explained
- **Load Test**: Normal expected traffic to verify system works under typical conditions
- **Stress Test**: Beyond normal capacity to find breaking point
- **Spike Test**: Sudden traffic increases to test auto-scaling
- **Volume Test**: Large amounts of data to test data handling
- **Endurance Test**: Extended periods to find memory leaks and performance degradation

### Best Practices
1. Start with smoke tests (1-2 users) to verify script works
2. Gradually increase load to find baseline performance
3. Monitor both client-side metrics and server-side resources
4. Run tests in environment similar to production
5. Coordinate with stakeholders before running high-load tests
6. Clean up test data after completion

### Troubleshooting
- High error rates: Check server logs, reduce load, verify endpoints
- Timeout errors: Increase timeout values, check network connectivity
- Memory issues: Reduce virtual users, optimize test scripts
- SSL/TLS errors: Verify certificates, update client configurations

## Results Analysis
The test will generate html format results. k6 provides built-in metrics and can export to various systems like InfluxDB + Grafana for real-time monitoring.