Right now there isn't a unified way to run indexing on deployments. If the user has chosen to run both Playwright and Browserstack/Playwright tests and the tests require indexing, the two different files deploymentPlaywrightTests.yml and deploymentBrowserStackTests.yml would both need to index, which would be time consuming and problematic.
Possible Solution
The best solution is to merge both deployment*Tests.yml files into a single workflow that includes an indexing job. These scan still be run simultaneously provided both wait until the index job is complete.
Because indexing is only run when a repo variable TESTING_NEEDS_SEARCH_INDEXING=true this can be skipped on sites that don't have search_api enabled and included in tests.
Right now there isn't a unified way to run indexing on deployments. If the user has chosen to run both Playwright and Browserstack/Playwright tests and the tests require indexing, the two different files deploymentPlaywrightTests.yml and deploymentBrowserStackTests.yml would both need to index, which would be time consuming and problematic.
Possible Solution
The best solution is to merge both deployment*Tests.yml files into a single workflow that includes an indexing job. These scan still be run simultaneously provided both wait until the index job is complete.
Because indexing is only run when a repo variable
TESTING_NEEDS_SEARCH_INDEXING=truethis can be skipped on sites that don't havesearch_apienabled and included in tests.