Dev/e2e

[Soare-Robert-Daniel]

Summary

Add E2E test infrastructure.

Will affect visual aspect of the product

NO

Check before Pull Request is ready:

• I have written a test and included it in this PR
• I have run all tests and they pass
• The code passes when running the PHP CodeSniffer
• Code meets WordPress Coding Standards for PHP, HTML, CSS and JS
• Security and Sanitization requirements have been followed
• I have assigned a reviewer or two to review this PR (if you're not sure who to assign, we can do this step for you)

Closes #411

[pirate-bot]

Plugin build for c6e6300 is ready 🛎️!

• Download PPOM - build 🔗

[abaicus]

@Soare-Robert-Daniel Things look good from the e2e tests perspective.

Any reason we're removing the caching steps?

[Soare-Robert-Daniel]

@abaicus, I took this advise Codeinwp/themeisle-sdk#240 (comment)

[abaicus]

We're removing the yarn cache as well. I don't think that we have that many or heavy dependencies in this particular repo, but I still think caching them would be useful as a general practice.

We can maybe look into updating the action to a more recent version: https://github.com/actions/cache?tab=readme-ov-file#example-cache-workflow

Up to you if you consider the dependencies might be worth caching. Otherwise, the PR looks good.

[Soare-Robert-Daniel]

@abaicus, I Did a little research and found out that setup-node has a built-in cache on top of action/cache.

This should simplify the approach https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#caching-packages-data

[abaicus]

@Soare-Robert-Daniel Great! That's pretty neat 👍🏻

[pirate-bot]

🎉 This PR is included in version 33.0.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀