[FEATURE] CI/CD Mode with Machine-Readable Output & Assertions

[kavix]

kurl's beautiful terminal output is counterproductive in CI/CD pipelines. No built-in assertions for testing APIs.

Proposed Implementation

kurl https://api.example.com --ci --format json

(machine-readable, no colors)

kurl https://api.example.com --expect-status 200

kurl https://api.example.com --expect-json '.status' 'ok'

kurl https://api.example.com --expect-header 'Content-Type' 'application/json'

kurl https://api.example.com --expect-response-time < 500ms

Exit codes: 0 = all pass, 1 = any fail

JUnit XML / TAP output for test result aggregation

Why this matters

API testing in CI/CD is typically done with heavy frameworks (Postman, REST Assured). kurl could replace them for simple smoke tests.

Acceptance Criteria

• --ci flag for non-interactive output
• --format json|xml|tap for machine parsing
• Status code assertions
• JSON path assertions
• Header assertions
• Response time assertions
• JUnit XML export
• Proper exit codes for CI integration