feat: allow pipeline test case to define the expected output based on service versions constraints #2114
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.
This PR essentially allows to specify a different expected output for a given pipeline test case based on given version constraints of running stack services. Such a feature is required to handle gracefully cases as the one captured here where the normal CI tests are passing as the stack version is defined by the minimum one required by the package manifest. However, testing it with a higher version of the stack, although not required to be the minimum supported, it results in different expected outputs
An example of an integration package that this PR could be used with can be found here. Here we define different expected outputs for
test-cisco-ios.log
andtest-asr920.log
depending on the elasticsearch version of the running stack