Zero Configuration
Drop a .httptests folder in your repo and go. No complex setup, no learning curve - just simple YAML and JSON.
Test your APIs, proxies, and microservices in CI/CD with zero configuration and Docker isolation
Add a test suite to your repository:
# .httptests/config.yml
mock:
network_aliases:
- backend
nginx:
environment:
ENV_VAR: value// .httptests/test.json
{
"hosts": {
"api.example.com": [
{
"paths": ["/health"],
"method": "GET",
"expectedStatus": 200,
"expectedResponseHeaders": [
["Content-Type", "application/json"]
]
}
]
}
}# .github/workflows/test.yml
name: HTTPTests
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: serviceguards-com/httptests-action@v2
with:
httptests-directory: .That's it! Your HTTP integration tests will now run on every push and pull request.
| Feature | HTTPTests | curl scripts | Postman/Newman | Custom Framework |
|---|---|---|---|---|
| Setup Time | < 5 minutes | Manual | 15-30 minutes | Hours |
| Docker Isolation | ✅ Built-in | ❌ Manual | ❌ Manual | ❌ Manual |
| Multi-Service | ✅ Yes | ⚠️ Complex | ⚠️ Limited | ⚠️ Custom |
| CI Integration | ✅ Native | ⚠️ Manual | ✅ Yes | ⚠️ Custom |
| Learning Curve | Low | Low | Medium | High |
Test REST APIs, GraphQL endpoints, and webhooks with comprehensive assertions on status codes, headers, and response bodies.
Validate reverse proxy configurations, header transformations, routing rules, and upstream forwarding behavior.
Test service-to-service communication, load balancing, service discovery, and API gateway configurations.
Verify load balancer behavior, health checks, failover scenarios, and request distribution.