What is CI/CD Pipeline Testing Strategy?

Question

Accepted Answer

**Testing Strategy** — comprehensive testing approach in CI/CD pipelines.

```yaml
# GitHub Actions multi-stage testing
name: Test Pipeline
on: [push, pull_request]

jobs:
  unit-tests:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4
    - run: npm ci
    - run: npm run test:unit -- --coverage
    - uses: actions/upload-artifact@v4
      with:
        name: coverage
        path: coverage/

integration-tests:
    needs: unit-tests
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:15
        env:
          POSTGRES_PASSWORD: test
        ports: ["5432:5432"]
      redis:
        image: redis:7
        ports: ["6379:6379"]
    steps:
    - run: npm run test:integration

e2e-tests:
    needs: integration-tests
    runs-on: ubuntu-latest
    steps:
    - uses: cypress-io/github-action@v6
      with:
        start: npm run dev
        wait-on: http://localhost:3000

security-scan:
    runs-on: ubuntu-latest
    steps:
    - uses: aquasecurity/trivy-action@master
      with:
        scan-type: fs
        severity: HIGH,CRITICAL
```

**Test Pyramid:**
- Unit: fast, many, isolated.
- Integration: moderate speed, service dependencies.
- E2E: slow, full stack, few.
- Security: SAST, DAST, dependency scanning.

DevOps: What is CI/CD Pipeline Testing Strategy?