Repository navigation
Run the scenarios of each package in parallel workers - #82
Merged
Merged
Conversation
Run every suite through the run-behat-tests runner of wp-cli/wp-cli-tests instead of calling Behat directly, so that WP_CLI_TEST_PARALLEL spreads its scenarios over several workers and a rerun covers exactly the scenarios that failed. Also fixes the name of the framework suite in test-source, which made TEST_PACKAGE=all skip it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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
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.
Uses the parallel runner of
wp-cli/wp-cli-tests(5.5) for the source and Phar suites:bin/test-sourceandbin/test-pharnow callvendor/bin/run-behat-tests --suite <package>instead ofvendor/bin/behat, withBEHAT_FEATURES_FOLDERpointing at the package's features. The runner derives the environment tags from there, as before. Calling it also enablesWP_CLI_TEST_PARALLEL, and a rerun after a parallel run covers exactly the scenarios that failed.WP_CLI_TEST_PARALLELto 4 workers, one per core of the runner.composer prepare-testsalready lets the test user create the per-worker databases.WP_CLI_TEST_DOCKER). The containers don't receiveWP_CLI_BIN_DIRor the temporary directory that holds the downloaded Phar, so the Phar legs would quietly test the source.wp-cli-/wp-cliintest-source, which madeTEST_PACKAGE=allskip the framework suite.Tested locally on
cron-command, from source and with the nightly Phar: 27 scenarios across 4 workers, all passing.🤖 Generated with Claude Code