[wp-trac] [WordPress Trac] #53945: Local test workflow changes for installing Composer dependencies

[WordPress Trac]

#53945: Local test workflow changes for installing Composer dependencies
------------------------------------------------+--------------------------
 Reporter:  hellofromTonya                      |       Owner:  johnbillion
     Type:  task (blessed)                      |      Status:  reopened
 Priority:  normal                              |   Milestone:  5.9
Component:  Build/Test Tools                    |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch has-testing-instructions  |     Focuses:
------------------------------------------------+--------------------------

Comment (by hellofromTonya):

 == Test Report

 === Env

 - node: 14.17.0
 - npm: 6.14.13
 - Docker Desktop: 3.5.2
 - WordPress: `trunk`
 - OS: macOS Big Sur 11.5.2
 - Command-Line tool: iTerm2 3.4.8

 === First run steps

 Set up a clean first run:
 - Delete the container in the Docker Desktop app
 - `Clean/Purge data` in the Docker Desktop app
 - Delete the `node_modules` and `vendor` folders
 - Delete the `composer.lock` file
 - Clear the local cache:
    - `npm cache clean --force`
    - `composer clearcache`
 - Fetch and merge the latest from `trunk`:
    - `git fetch upstream`
    - `git merge upstream/master`
 - Start up the npm Docker environment:
    - `npm install`
    - `npm run build:dev`
    - `npm run env:start`
    - `npm run env:install`

 Clock the time delay once the message appears:
    - Test Composer directly by running `composer update`.
    - Clean up:
      - Delete `vendor` folder and `composer.lock` file
      - Run `composer clearcache`
    - Test npm by running `npm run test:php -- --group cron`
    - Clean up again
    - Now test `npm run test:php-composer -- --group cron`


 === Repeat run steps

 After the first run (see above), clock the time delay once the message
 appears but don't do the clean up step.

 Repeatedly run:

 - `composer update` and then note the time delay once the message appears.
 Repeat.
 - Repeat for `npm run test:php -- --group cron`
 - Repeat for `npm run test:php-composer -- --group cron`

 === Results

 The noted time delay after the `Use the 'composer fund' command to find
 out more!` message appears:

 - `composer update`
    - First run: 2.36 seconds
    - Rerunning: 1.02 sec, 0.96 sec, 1.13 sec, 1.15 sec

 - `npm run test:php -- --group cron`
    - First run: 18.85 secs
    - Rerunning: 2.52 sec, 1.35 sec, 1.60 sec, 1.59 sec, 1.73 sec


 - `npm run test:php-composer -- --group cron`
    - First run: 19.22 secs
    - Rerunning: 1.14 sec, 1.93 sec, 1.55 sec, 2.06 sec, 1.83 sec

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53945#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform