[E2E][QIT] Add GitHub Actions workflow for QIT E2E tests in CI #11054
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
- Introduced WP-CLI commands for QIT setup and status checks to assist in development environments. - Created a new class `WP_CLI_QIT_Dev_Command` for handling Jetpack connection setup and account data refresh. - Added E2E test runner script and configuration for QIT, including basic tests for WooCommerce Payments functionality. - Updated package.json to include a new script for running QIT E2E tests. - Enhanced default environment configuration for QIT testing with necessary credentials. - Implemented setup script for WooCommerce Payments E2E tests to configure products, customers, and Jetpack connections. - Added ESLint configuration for E2E tests to accommodate Playwright testing framework. - Created initial E2E test cases to verify basic functionality and plugin activation.
…nce setup functions, and add connection validation tests
- Add .github/workflows/qit-e2e.yml with comprehensive CI setup - Support multiple WooCommerce and PHP version combinations - Enable manual workflow dispatch with custom parameters - Update e2e-runner.sh to handle CI environment options - Add CI.md documentation explaining workflow usage and setup The workflow runs on PR, push to main branches, scheduled, and manual dispatch. Includes proper authentication and environment variable handling for CI context.
Security improvements: - Add GitHub Actions log masking for all sensitive tokens - Use environment variables instead of command-line arguments in WP-CLI - Update WP_CLI_QIT_Dev_Command to prioritize env vars over CLI args - Remove tokens from command-line to prevent exposure in process lists - Add comprehensive security documentation and best practices This prevents token leakage through: - Process lists (ps aux) - Command history - GitHub Actions logs - Error output and debugging info All tests continue to pass with enhanced security measures.
Collaborator
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. |
mgascam
force-pushed
the
dev/qit-e2e-workflows
branch
from
6efa26e to
07efbd5
Compare
mgascam
force-pushed
the
dev/qit-e2e-workflows
branch
from
ea9f527 to
c12814c
Compare
mgascam
changed the title
Member
if they fail against |
mgascam
force-pushed
the
dev/qit-e2e-workflows
branch
from
556fca6 to
c3134c8
Compare
Contributor
Author
|
Closing in favor of #11082 |
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-5337
This PR bulds on top of #11049. It adds a GitHub Actions workflow for running QIT E2E tests in our CI pipeline.
Changes proposed in this Pull Request
.github/workflows/qit-e2e.ymlto run QIT E2E tests automatically on PRs, pushes to main branches, and daily scheduled runsTesting 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