Terminal
Terminal/Skill
Guides writing and debugging elastic-package tests: pipeline fixtures, system tests with mock APIs, and script tests for failures and upgrades.
By Elastic
Works with
npx skills add elastic/integration-skills --skill integration-testingLoad this skill whenever tasks include:
.log/.json inputs, *-expected.json output, config files)_dev/test/system/, _dev/deploy/, mock APIs, 0-hits failures)Do not use this skill as the primary guide for:
ingest-pipelines)cel-programs)elastic-package-cli)| Test type | Load when | Reference file |
|---|---|---|
| Pipeline tests | Writing fixtures, config files, expected output, debugging pipeline test failures | references/pipeline-testing.md |
| System tests (generic) | Always load for any system test work — config fields, commands, teardown, debugging | references/system-testing.md |
| Script tests | txtar failure/error tests, upgrade tests, mock services embedded in txtar | references/script-testing.md |
In addition to the generic system-testing.md, load the reference file matching your data stream's input type:
| Input type | Reference file |
|---|---|
cel | references/system-testing-cel.md |
tcp, udp | references/system-testing-tcp-udp.md |
http_endpoint | references/system-testing-http-endpoint.md |
logfile, filestream | references/system-testing-logfile.md |
kafka, gcp-pubsub | references/system-testing-kafka-pubsub.md |
aws-s3, gcs, azure-blob-storage, azure-eventhub | references/system-testing-cloud-skip.md |
When an integration supports multiple input types, load the generic reference plus each applicable input-type reference.
When working across multiple test types in one task (e.g. creating a new data stream end-to-end), load all applicable reference files.
references/pipeline-testing.md — directory layout, naming conventions, fixture formats, config options, expected output format and review, core workflow, fixture scenario coverage, data anonymization, troubleshootingreferences/system-testing.md — generic system test reference: required layout, config fields, core commands, teardown failures, sample_event.json verification, general debuggingreferences/system-testing-cel.md — CEL mock API wiring, 0-hits debugging for CEL, variable-capture patternsreferences/system-testing-tcp-udp.md — TCP/UDP log sender pattern with elastic/stream, signal coordination, port alignmentreferences/system-testing-http-endpoint.md — webhook/HTTP endpoint testing with STREAM_PROTOCOL=webhook, auth headersreferences/system-testing-logfile.md — Alpine container + SERVICE_LOGS_DIR pattern for logfile/filestream inputsreferences/system-testing-kafka-pubsub.md — Kafka broker + stream producer, Pub/Sub emulator patternsreferences/system-testing-cloud-skip.md — when and why to skip system tests for cloud storage inputs (aws-s3, gcs, azure-blob-storage, azure-eventhub)references/script-testing.md — txtar format, env smoke test, system-level skeleton, mock service docker-compose and config.yml, upgrade test pattern, pitfalls, full o365 examplesreferences/builder-setup-subagent-guidance.md — subagent operating manual for wiring data collection (docker-compose, sample logs, agent stream template, system test config, manifest var cleanup) for non-CEL data streams. The orchestrator dispatches subagents by passing this file's path in the task prompt; the subagent reads it itself in its own fresh context. Do NOT embed/paste its contents into the task prompt.references/builder-system-test-subagent-guidance.md — subagent operating manual for running elastic-package test system --generate after pipeline work completes (any testable input). Same dispatch rule as above: orchestrators pass the path, the subagent reads the file itself.