[System test runner] Support for multiple tests per data stream #208
Labels
enhancement
New feature or request
Comments
|
@andrewkroh Does each of these have a separate stream template? |
|
Yes, as an example this package has a template for the UDP input and a logfile input. https://github.com/elastic/integrations/tree/0d55adaa4ea33e94b05f5c5106cc22c845b720ae/packages/checkpoint/data_stream/firewall/agent/stream |
|
👍 Each template should allow its own test. I'm wondering if we should go so far to allow each template multiple tests? |
5 tasks
adriansr
added a commit
that referenced
this issue
Jan 12, 2021
Updates the system tests runner so that multiple test-*-config.yml files
can be included in <data_stream>/_dev/tests/system. This allows testing
multiple inputs and/or different configuration options per data stream.
Example test for two inputs:
test-tcp-input.yml:
input: tcp
service: bluecoat-director-tcp
vars: ~
data_stream:
vars:
tcp_host: 0.0.0.0
tcp_port: 9514
test-udp-input.yml:
input: udp
service: bluecoat-director-udp
vars: ~
data_stream:
vars:
udp_host: 0.0.0.0
udp_port: 9514
The service tags allows to uses different containers for the tests.
In this case, to generate traffic using different protocols.
Sample docker-compose.yml in <package>/_dev/deploy/docker:
version: '2.3'
services:
bluecoat-director-tcp:
tty: true
build: .
volumes:
- ./logs:/logs/:ro
command: /stream -proto tcp -dest elastic-agent:9514 /logs/generated.log
bluecoat-director-udp:
tty: true
build: .
volumes:
- ./logs:/logs/:ro
command: /stream -proto udp -delay 100ms -dest elastic-agent:9514 /logs/generated.log
Relates #208
|
Implemented in #209. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Data streams can have multiple input options such as logfile, syslog over UDP, and syslog over TCP. In order to have test coverage over all of the supported input configurations we need a way to execute more than one system test per data stream.
Current a single test is declared in
data_stream/<name>/_dev/test/system/config.yml. If we can expand this to allow more than one test definition then we'll be able to expand test coverage.The text was updated successfully, but these errors were encountered: