Move qit test to test packages #11145
Draft
Conversation
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
added 2 commits
November 20, 2025 17:20
Contributor
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. |
Contributor
|
Size Change: 0 B Total Size: 875 kB ℹ️ View Unchanged
|
MrJnrman
changed the title
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.
Changes proposed in this Pull Request
Move QIT custom tests to new test package architecture
Testing instructions
The site that QIT spins needs an onboarded account. Follow this steps to get the JetPack tokens:
./qit run:e2e woocommerce-payments --test-package=<path to test package folder> --source <path to woo payments zi>Note: The qit binary used must be the one in the trunk of the qit-cli repo and must already be authenticated with a vendor account that has access to woocommerce-payments.
Example of a failed run: https://qit.woo.com/?qit_results=4923604.TEbVeRh9ECEtweOanYviyZvRiyRuVf7trEPc3nms0SePEOvtpoWmP93ThruYV3cZ
Example of a passing run: https://qit.woo.com/?qit_results=4924041.A7YZKu5v1pk4NGCCDHli75zMtMY2arC4RPKeO7eFuHS1SCwxEyTMrr5k82hVF2DY