Skip to content

Conversation

Bashev
Copy link
Contributor

@Bashev Bashev commented May 16, 2023

Description (*)

Related Pull Requests

https://github.com/magento-gl/magento2-infrastructure/pull/26

Fixed Issues (if relevant)

  1. Fixes GTag not send transaction prices and totals. #37348

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

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/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented May 16, 2023

Hi @Bashev. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:
  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: pending review labels May 16, 2023
@Bashev
Copy link
Contributor Author

Bashev commented May 16, 2023

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

# Conflicts:
#	app/code/Magento/GoogleGtag/Block/Ga.php
#	app/code/Magento/GoogleGtag/Test/Unit/Block/GaTest.php
@Bashev
Copy link
Contributor Author

Bashev commented Sep 13, 2023

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@sinhaparul sinhaparul added the Project: Community Picked PRs upvoted by the community label Sep 13, 2023
@engcom-Hotel
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

Copy link
Contributor

@engcom-Hotel engcom-Hotel left a comment

Choose a reason for hiding this comment

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

Hello @Bashev,

Thanks for the contribution!

Please review my comment below and fix the build failures below.

Thanks

@engcom-Echo
Copy link
Contributor

@magento run all tests

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

@magento run Functional Tests CE

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

✔️ QA Passed

Preconditions:

  • Install fresh Magento 2.4-develop

Manual testing scenario:

  1. We have follow steps from comment
  2. Create Coupon and Use same coupon.

Before: ✖️  Coupon and Discount data is not present in gtag data
Screenshot 2023-12-13 at 6 26 35 PM

After: ✔️  Coupon and Discount is present in gtag data
Screenshot 2023-12-13 at 6 32 04 PM

Builds are failing, Hence moving to Extended Testing

@engcom-Echo
Copy link
Contributor

@magento run all tests

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

@magento run Integration Tests,Functional Tests B2B

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

Functional Tests B2B builds are green and Static Tests are known failure.
Hence moving it to Merge In Progress

@engcom-Charlie
Copy link
Contributor

Hi @Bashev,

As per the static test failure:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37504/2e4c1e56737a74d963734ed5da13d4d0/Statics/console-error-logs.html

The view layer changes have been detected in the GoogleGtag module. The GoogleGtagGraphQl module is expected to be updated to reflect these changes. The test failure can be ignored if the changes can not be covered with GraphQL API.

In order to proceed further we need to green build so can you please look into this and update the PR accordingly. Moving this to Changes Requested now.

Thank you!

image

@engcom-Charlie
Copy link
Contributor

Hi @Bashev,

As mentioned in above comment, static test failure need to be fix in order to proceed further on this PR. Currently closing this PR, please feel free to reopen for any updates from your end.

Thank you!

@Bashev
Copy link
Contributor Author

Bashev commented Feb 12, 2024

@engcom-Charlie I cannot find the module mentioned in the test GoogleTagGraphQl, probably i miss something, but in the repository this module is not visible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Project: Community Picked PRs upvoted by the community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GTag not send transaction prices and totals.
6 participants