Integration Tests: DOM Assertion class

[lbajsarowicz]

Description (*)

We have plenty of integration tests that make assertions on HTML code:

With assertContains or preg_match. This is not the right approach for making assertions on HTML and the correct approach should be possible. The right approach is based on DOM tree.

Example:
https://github.com/magento/magento2/pull/27606/files#diff-dcb208981e520970637c75ff2d89eafcR169-R173

Expected behavior (*)

We need the DOM assertion class to be introduced to Integration Tests Framework

Benefits

Additional information

[m2-assistant]

Hi @lbajsarowicz. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@lbajsarowicz do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-33094 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[lbajsarowicz]

Still to be implemented.

[magento-engcom-team]

Hi @lbajsarowicz. Thank you for your report.
The issue has been fixed in #27606 by @lbajsarowicz in 2.4-develop branch
Related commit(s):

• 1ac923d3487a7ce8f65db2bd1191a9349a77c99d
• 16cb18d7edaf504e7de2899f6935d33f8fcc42d9
• f882122a3280f3b60706f87d9428f75b11a80112
• 82224a62f63955d1c070e2509298e27acc52cdd4
• cd895a5f9cc363166d229888f1780c54255f7710
• d4b80830e4e21ed16e50170dcefb6468aa3a7ea3

The fix will be available with the upcoming 2.4.0 release.

[lbajsarowicz]

The issue still needs to be implemented.
What is actually closed in scope of the PR mentioned above was use of such DOM assertions there.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!