[buddypress-trac] [BuddyPress Trac] #6382: Add dynamic Grunt Watch task

[buddypress-trac]

#6382: Add dynamic Grunt Watch task
------------------------------+-------------------------------------
 Reporter:  netweb            |       Owner:  netweb
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:  Awaiting Contributions
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |
------------------------------+-------------------------------------

Comment (by iandunn):

 An alternative approach would be to setup [https://github.com/spatie
 /phpunit-watcher/ phpunit-watcher] or [https://pestphp.com/ Pest].

 phpunit-watcher is used in Gutenberg, wordcamp.org, and several other
 wporg repos. They've merged several PRs I've sent when I ran into bugs,
 but it doesn't seem to be as well maintained as Pest. Pest
 [https://pestphp.com/docs/writing-tests uses Jest-like syntax], which I
 don't personally prefer, but that may just be because I'm a grumpy old man
 :) It looks like it'll also work with traditional PHPUnit tests, though,
 so nothing has to be migrated.

 I imagine either would be much easier to work with than Grunt, which is
 usually unpleasant in my experience.

 I think the most recent time I set up phpunit-watcher was for `wporg-two-
 factor`, so that might be the best config to reference:

 https://github.com/WordPress/wporg-two-
 factor/blob/c7b22f288d4943410e9a3cc301e6d1c4461575eb/phpunit-
 watcher.yml.dist

 https://github.com/WordPress/wporg-two-
 factor/blob/c7b22f288d4943410e9a3cc301e6d1c4461575eb/composer.json#L41-L44


 See also https://github.com/WordPress/gutenberg/pull/27058
 Related: https://core.trac.wordpress.org/ticket/50412

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6382#comment:28>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac