Skip to content

Fix an issue with extended data array entity #727

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

Merged
merged 4 commits into from
Jun 4, 2020
Merged

Conversation

okolesnyk
Copy link
Member

Description

Fixed Issues (if relevant)

  1. magento/magento2-functional-testing-framework#<issue_number>: Issue title
  2. ...

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/verification tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)
  • Changes to Framework doesn't have backward incompatible changes for tests or have related Pull Request with fixes to tests

Copy link
Contributor

@jilu1 jilu1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix looks good!
One comment about the DevDocsTest and please fix verification test

@@ -48,8 +48,8 @@
</actionGroup>

<assertEqualsCanonicalizing stepKey="assertMergedArray">
<actualResult type="array">{{MessageData.numbers}}</actualResult>
<expectedResult type="array">["Something New", "0", "1", "2", "3"]</expectedResult>
<actualResult type="array">{{ExtendedMessageData.numbers}}</actualResult>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we keep the original MessageData assertion and add a new assertion for ExtendedMessageData so that we don't lose test coverage of the previous fix?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we lose it.
In 1 assertion we cover both.
Because MessageData gets merged and then on top of it we merge ExtendedMessageData.numbers

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not a big deal. I am ok with either way.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 55.926% when pulling 9236244 on DataEntity into cdc5188 on develop.

@coveralls
Copy link

coveralls commented Jun 3, 2020

Coverage Status

Coverage remained the same at 55.91% when pulling a0e287e on DataEntity into cdc5188 on develop.

@okolesnyk okolesnyk requested a review from jilu1 June 3, 2020 22:32
@okolesnyk
Copy link
Member Author

Copy link
Contributor

@jilu1 jilu1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@okolesnyk okolesnyk merged commit fd2da03 into develop Jun 4, 2020
@tomreece tomreece deleted the DataEntity branch July 27, 2020 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants