Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Add document equivalency test case to end to end tests #290

Closed
Tracked by #16
leehinman opened this issue Mar 28, 2023 · 1 comment · Fixed by elastic/beats#36536
Closed
Tracked by #16

Add document equivalency test case to end to end tests #290

leehinman opened this issue Mar 28, 2023 · 1 comment · Fixed by elastic/beats#36536
Assignees
Labels
Team:Elastic-Agent Label for the Agent team

Comments

@leehinman
Copy link
Contributor

Once end to end tests exist that can run elastic-agent both with and without the shipper, we should add tests similar to the code https://github.com/leehinman/docdiff to verify that the documents that are ingested are equivalent. This will be especially useful when processors are added to the shipper.

@leehinman
Copy link
Contributor Author

I built an integration test on top of elastic/beats#36349, that compared documents going through the shipper and not. The documents are not the same. input.type is different.

leehinman added a commit to leehinman/beats that referenced this issue Sep 8, 2023
leehinman added a commit to leehinman/beats that referenced this issue Sep 8, 2023
leehinman added a commit to elastic/beats that referenced this issue Sep 12, 2023
* add equiv check to filebeat as shipper test

Closes elastic/elastic-agent-shipper#290

* update go.mod & NOTICE.txt

* fix unchecked error
Scholar-Li pushed a commit to Scholar-Li/beats that referenced this issue Feb 5, 2024
* add equiv check to filebeat as shipper test

Closes elastic/elastic-agent-shipper#290

* update go.mod & NOTICE.txt

* fix unchecked error
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants