[wp-trac] [WordPress Trac] #50401: Tests: Move tests into Github Actions

WordPress Trac noreply at wordpress.org
Tue Oct 13 19:38:20 UTC 2020


#50401: Tests: Move tests into Github Actions
-------------------------------------+-----------------------------
 Reporter:  whyisjake                |       Owner:  desrosj
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  Future Release
Component:  Build/Test Tools         |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+-----------------------------

Comment (by desrosj):

 A few more things that just came to me.

 - The JSHint linting should eventually be moved to the coding standards
 workflow, making the JavaScript workflow strictly about QUnit testing.
 However, the action I [https://github.com/wearerequired/lint-
 action/issues/90 used for the PHPCS linting does not yet support JSHint].
 There is [https://core.trac.wordpress.org/ticket/31823 a ticket to move
 away from JSHint to ESLint] (the docs related JS scans already are, see
 #43828), but I think we should explore that separately. For the purpose of
 moving our tests runners to GHA, we can continue to use the Grunt command
 for now.
 - [attachment:"50401.diff"] and the PR intentionally contain a small
 number of PHPCS and PHP compatability issues in order to demonstrate that
 the workflows are correctly flagging those issues.

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


More information about the wp-trac mailing list