QUnit should be testable on both compiled and minimized JS

[jorbin]

Discussed in IRC ​https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-10-30&sort=asc#m717593 , we want to make our testing more verbose.

[jorbin]

To run, I've added the new task

grunt test:compiled

[jorbin]

The new patch uses copy and processContent instead of adding another dependency as suggested by Nacin.

[ocean90]

Re 25781.2.diff​: Seems like you have mixed tabs/whitespaces again. :)

[jorbin]

Thanks ocean90, at least I spelled everything correctly (I think).

25781.3.diff should fix that

[kadamwhite]

Cleaned up spacing in 25781.3.diff, removed spaces-to-tabs conversion within a comment

[kadamwhite]

I edited 25781.3.diff to unify the whitespace style, and remove an edit to an unrelated comment that got caught in the spaces-to-tabs find/replace.

[nacin]

In 26063:

Add grunt qunit:compiled to run the QUnit tests on the compiled JS.

props jorbin, kadamwhite.
fixes #25781.

[nacin]

In 26064:

Add grunt phpunit which runs three tasks: phpunit, ajax tests, and phpunit as multisite.

You can also run grunt phpunit:default, grunt phpunit:ajax, and grunt phpunit:multisite separately.

grunt test now runs the qunit task (both compiled and uncompiled scripts) and the phpunit tasks.

props bpetty.
fixes #25854, see #25781.

[jorbin]

We should ignore the created compiled.html file so that after running the tests it doesn't show up in an svn status.

[nacin]

qunit:compiled runs clean:qunit when done, removing compiled.html. Of course, it is still possible for it to end up left behind.

[jorbin]

Hmm, mine was left before but reran it and this time it wasn't.

Overall, this seems like a bad idea as it makes it harder to test in browsers. Right now to test in browsers other than phantomjs, we can't run qunit:compiled, we need to run each command individually. If we have clean:qunit run before copy:qunit-compiled instead of after qunit, we gain this ability.

[nacin]

In 26108:

Don't remove the compiled.html QUnit file. Ignore it instead.

props jorbin.
fixes #25781.

[nacin]

Now I remember why I did it the other way. The problem is if you run grunt qunit later, the compiled QUnit will be run, but it will be out of date.

Two options. One is grunt qunit:index and grunt qunit:compiled. Ideally, though, grunt qunit can be used just for qunit:index. This is not possible without a big hack and/or ​this enhancement upstream, as found by jorbin.

The second one is a bit of a hack, as attached as 25781.5.diff​. Ideally, qunit:compiled runs it on the uncompiled as well, but I couldn't get it to execute qunit then set the config then re-execute qunit. It's a queueing system and things work async and such.

[jorbin]

A second hacky option as attached as 25781.6.diff is to use filter to filter out everything but index.html when we are running just qunit. Both my approach and Nacin's are far from perfect but I think keeping the hack in the config makes it a bit more readable. Either way, inline docs as to why we are doing it this way (or a link to the ticket) would be helpful.

[boonebgorges]

In 31344:

Use minified jquery-ui-core file during qunit:compiled Grunt task.

[30989] made jQuery UI Core a dependency for QUnit tests. This change did not
account for the fact that jQuery JS assets are minimized (and non-minimized
versions unavailable) when grunt copy populates the /build directory. To
ensure that QUnit tests pass when run during grunt qunit:compiled, we
manually fix the asset path to read 'core.min.js'.

See #25781.