-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update system test docs to include new Elastic Agents #1830
Update system test docs to include new Elastic Agents #1830
Conversation
/test |
docs/howto/system_testing.md
Outdated
@@ -411,6 +428,7 @@ for system tests. | |||
| service_notify_signal | string | | Signal name to send to 'service' when the test policy has been applied to the Agent. This can be used to trigger the service after the Agent is ready to receive data. | | |||
| skip.link | URL | | URL linking to an issue about why the test is skipped. | | |||
| skip.reason | string | | Reason to skip the test. If specified the test will not execute. | | |||
| skip_ignored_fields | array string | | List of fields to be skipped when perfoing mapping validation. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding field introduced in #1738
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
docs/howto/system_testing.md
Outdated
@@ -40,7 +41,9 @@ Packages have a specific folder structure (only relevant parts shown). | |||
|
|||
To define a system test we must define configuration on at least one level: a package or a data stream's one. | |||
|
|||
First, we must define the configuration for deploying a package's integration service. We can define it on either the package level: | |||
If the package does not require a service for testing, there is no need to define any service deployer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note about not requiring anymore a service deployer.
docs/howto/system_testing.md
Outdated
@@ -411,6 +428,7 @@ for system tests. | |||
| service_notify_signal | string | | Signal name to send to 'service' when the test policy has been applied to the Agent. This can be used to trigger the service after the Agent is ready to receive data. | | |||
| skip.link | URL | | URL linking to an issue about why the test is skipped. | | |||
| skip.reason | string | | Reason to skip the test. If specified the test will not execute. | | |||
| skip_ignored_fields | array string | | List of fields to be skipped when perfoing mapping validation. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
/test |
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
💚 Build Succeeded
History
cc @mrodm |
Part of #787
This PR updates the documentation related to System tests to include information about the independent Elastic Agents developed, still in technical preview.