The purpose of this test is to verify that the current version of the shipper client is able to successfully publish events to the shipper server. We could take the following steps:

1. We run filebeat and the shipper server as binaries or containers, no code dependencies
2. We pre-define configuration that would allow:
   2.1. filebeat to read a file that has N events
   2.2. filebeat to alter the consumed events from the file (simple processing, like adding a field)
   2.3. filebeat to publish events from the file to the shipper server
   2.4. the shipper server to output these events to a file
3. We pre-define an input file and an expected output file according to the configured alternation rules. The alternation is needed to make the difference more obvious and mark that events passed the pipeline
4. We run the pipeline until the shipper server has written N events to the file or time is up (perhaps watch logs in debug more or use wc -l on the output file.

Dependencies:

• Publishing the shipper as a docker image for consumption by the Beat output tests.
• Allow running the shipper in standalone mode independently of the agent elastic-agent-shipper#83