[wp-trac] [WordPress Trac] #51446: CORS issues with QUnit while running tests

[WordPress Trac]

#51446: CORS issues with QUnit while running tests
-------------------------------------------------+-------------------------
 Reporter:  garrett-eclipse                      |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Build/Test Tools                     |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:  javascript
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by garrett-eclipse):

 Thanks @iandunn, I'm not alone ;)

 That being said, while coming back to look at this I ran `grunt test`
 before I realized MAMP was enabled... and it ran... reminding me I have
 Laravel Valet running on localhost itself and MAMP is localhost:8888.
 That being said opening the qunit file directly using either localhost or
 localhost:8888 to be served by either MAMP or Valet the tests work fine.
 It's only via command line this seems to be an issue.
 *Mainly mentioning to remove direct relation to MAMP there.

 From searches I wonder if we enable `--disable-web-security` similar to
 seen here for the qunit setup in Grunt.js, example;
 https://github.com/gruntjs/grunt-contrib-
 qunit/issues/158#issuecomment-511819334

 Is there a need for CORS checks during qunit testing?

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