PROVIDER - HTTP tests written in plain text
Hurl
Hurl describes HTTP requests and assertions in 1 plain text file, supporting 6 or more assertion families with chained requests and variable passing, running as a single binary in 3 or more pipelines under Apache 2.0 from Orange; the gaps are no GUI and limited expressiveness.
4.1pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
Hurl is an HTTP testing tool maintained by the Orange open source team, describing requests, assertions and variable passing in plain text files.
In the development tools category it is interface regression tooling: write tests in a request file format, yet assert, chain and run them in CI.
Key Strengths
- Plain text cases: versionable and reviewable
- Strong assertions: 6 or more families
- Flow chaining: variables across requests
- Single binary: simple install
- Auditable open source: Apache 2.0
Product Ecosystem
Platform capabilities
Request definition and assertions, variables and templates, chained calls, HTML report export and request syntax conversion.
Integrations
Fits GitHub Actions, GitLab CI and Jenkins pipelines and combines with Docker and Kubernetes health checks.
Typical scenarios
Interface regression tests, contract smoke checks, post-release verification and monitoring script reuse.
Limitations
- No GUI: debugging is command line based
- Expressiveness: complex logic needs scripting
- Community size: relatively few resources
- Reporting: visualisation needs external tools
Use Cases
- Interface regression and smoke tests (★★★★★): text cases age well
- Post-release verification (★★★★☆): scripts get reused
- Complex business flows (★★★☆☆): pair with scripts
- Low-code test platforms needs (★★☆☆☆): not applicable
Pricing
| Item | Price | Notes |
|---|---|---|
| Hurl | $0 | Apache 2.0, free and open source |
| Installation | $0 | brew, apt or cargo |
| Enterprise support | Community | No commercial licence fee |
FAQ
How is it different from curl?
Hurl extends a plain request syntax with assertions, variables and chained execution.
Does it support file uploads?
Yes, multipart requests and file fields are supported.
Can it produce reports?
JUnit and HTML report formats are available for CI integration.
Does it handle HTTPS and certificates?
Yes, client certificates and verification options are configurable.
Code Examples
# demo.hurl
GET https://api.example.com/orders/1
HTTP 200
[Asserts]
jsonpath "$.id" == 1
header "Content-Type" contains "application/json"
POST https://api.example.com/orders
{
"sku": "demo-1",
"qty": 2
}
HTTP 201
[Captures]
order_id: jsonpath "$.id"
GET https://api.example.com/orders/{{order_id}}
HTTP 200
[Asserts]
jsonpath "$.qty" == 2
# Run tests and export an HTML report
hurl --test --report-html report demo.hurl
# Run a whole directory in parallel
hurl --test --parallel --jobs 4 tests/
Community & Resources
- Website: https://hurl.dev/
- Documentation: https://hurl.dev/docs/manual.html
- Source repository: https://github.com/Orange-OpenSource/hurl
Articles
- 01 GitLab CI/CD Best Practices: From Beginner to Production-Grade Pipelines 07-18
- 02 Prometheus Monitoring System Setup: From Metric Collection to Alert Notifications 07-18
- 03 Ansible Automation Ops Guide: From Configuration Management to Application Deployment 07-18
- 04 Docker Beginner Tutorial: From Installation to Containerized Web Deployment 07-18
- 05 API Integration Guide: REST vs GraphQL Comparison and Selection 07-18
- 06 GitHub Actions CI/CD Tutorial: Automated Build, Test, and Deployment 07-18
- 07 Docker Compose Multi-Container Deployment: Building Complete Application Orchestration 07-18
- 08 Kubernetes Deployment Guide for Beginners: Building a K8s Cluster from Scratch 07-18
- 09 Best VS Code Extensions 2026: Boost Your Development Productivity 07-18
- 10 Frontend Toolchain 2026: Vite / Next.js / Tailwind CSS Ecosystem 07-18