Preparations for custom E2E tests #10811
Draft
Conve 8000 rsation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
|
Size Change: 0 B Total Size: 1.26 MB ℹ️ View Unchanged
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes WOOPMNT-4988
Changes proposed in this Pull Request
WP_CLIcommands to:Due to the potential dangerous nature of such commands, those are only available in the
developmentandlocalenvironments.Bootstrapped QIT custom E2E tests with a draft version of
setup.shscript to cover the main steps to build a testing environment. It is not fully functional yet: initiating test drive mode doesn't work in my environment and I haven't fully figured out why.Because of QIT design, plugin release has to be built before running custom tests locally. Otherwise, it will be running tests with the latest released version.
Example command to run tests:
The
.envfile should containE2E_JP_BLOG_TOKEN,E2E_JP_USER_TOKENandE2E_JP_SITE_IDconstants. Those can be retrieved on a connected test site, using the code below to extract the blog id & tokens.Another option is to install Jetpack Beta Tester plugin, and enable Jetpack Debug. In the Jetpack Debug menu check the Broken Token and save. The Broken Token submenu will appear and will contain the aforementioned data.
Testing instructions
npm run changelogto add a changelog file, choosepatchto leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge