integration-test

End-to-end testing for a CLI against a live server instance involves executing verification scripts that interact with real data endpoints. This process validates functionality by checking detail endpoints, discovering metrics adaptively, and generating a human-readable coverage report.

Yes, you need jq and bash to verify CLI functionality against live instances. The verification process utilizes go build for compiling the CLI, alongside bash scripting and jq for executing the tests and parsing the endpoint responses.

Adaptive metric discovery in live instance testing is a mechanism that automatically identifies and tests real metrics from a live server. It ensures the CLI correctly retrieves and processes actual metric data rather than relying on static test fixtures.

To generate a human-readable coverage report for CLI verification, execute the integration test scripts against a live server. The script automatically compiles the results into a readable format detailing the test coverage and endpoint validation outcomes.

Live instance CLI verification tests are safe for production environments because they enforce read-only operations. The testing mechanism validates the absence of forbidden verbs and flags to ensure no mutating actions occur during endpoint checks.

To test a CLI against a live Traceway server, you need an authenticated user with a default project configured on the server. Additionally, the local environment must have Go, jq, and bash installed to support the build and script execution.