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

buddypress-trac noreply at wordpress.org
Fri Oct 6 18:15:18 UTC 2023


#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 prbot):

 ''This ticket was mentioned in
 [https://github.com/buddypress/buddypress/pull/172 PR #172] on
 [https://github.com/buddypress/buddypress/ buddypress/buddypress] by
 [https://profiles.wordpress.org/iandunn/ @iandunn].''
 This is an alternative approach for a test watcher to the Grunt approach
 in
 [https://buddypress.trac.wordpress.org/attachment/ticket/6382/6382.6.patch
 6382.6.patch]. phpunit-watcher is used in Gutenberg, wordcamp.org, and
 several other wporg repos.

 Pest may be a better alternative long term, but that might require a more
 substantial migration. There isn't any watcher right now, which makes
 testing less convenient (and therefore less likely). The ticket has been
 dormant for a long time, and this only took a few minutes to set up, so it
 seems like a good short/medium-term solution to me, even if folks
 eventually want to switch to Pest or something else. IMO it'd also be fine
 as a long-term solution.

 To test, run `composer update`, then something like `composer run
 test:watch -- --group=group,cache`. It should re-run the selected tests
 automatically when any PHP files in `src` or `tests` change.

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


More information about the buddypress-trac mailing list