[Metricbeat] Mocked Tests: Do not halt if doc check fails #11780
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the current behaviour, tests halt if doc checks can't find a field and the
-expected.json
file is not written. With this change, the file is written at least, helping identifying the issue.@ruflin I was wondering if descriptive errors which leads to the solution to developers and contributors are a way to go as a general rule. In this particular context, I was about to write a very long and descriptive error here because I realized that a field that exists in
{module}/{metricset}/_meta/fields.yml
can still be missing in rootfields.yml
and throw an error... which confused me for a while until I thought to try with amake update
. WDYT?