Skip to content
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

Cherry-pick #16493 to 7.x: Change the assertion for fileset modules #19869

Merged
merged 1 commit into from
Jul 14, 2020

Conversation

adriansr
Copy link
Contributor

@adriansr adriansr commented Jul 14, 2020

Cherry-pick of PR #16493 to 7.x branch. Original message:

What does this PR do?

In the previous module assertion we were checking the keys manually and
if they didn't match we would just output the raw dictionary into the
tests. This is not really useful because you have to either inspect them
manually or user a local diff to know what exactly changes.

This PR use DeepDiff to actually diff the two dictionary together and
will output diff of the two dictionnary. This make debugging a little
easier.

Why is it important?

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

In the previous module assertion we were checking the keys manually and
if they didn't match we would just output the raw dictionary into the
tests. This is not really useful because you have to either inspect them
manually or user a local diff to know what exactly changes.

This PR use DeepDiff to actually diff the two dictionary together and
will output diff of the two dictionnary. This make debugging a little
easier.

(cherry picked from commit fa506a6)
@adriansr adriansr added [zube]: In Review backport Team:Platforms Label for the Integrations - Platforms team labels Jul 14, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jul 14, 2020
@adriansr
Copy link
Contributor Author

I need this for #19868

That PR requires the diff'ing for system-tests to ignore the order of array elements in comparisons. This was the case in master, but in 7.x we're currently using a simpler comparison method.

@adriansr adriansr merged commit 00d0f18 into elastic:7.x Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Platforms Label for the Integrations - Platforms team [zube]: Done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants