FLUID-4753: Upgrade qunit to jquery's trunk, as well as introducing "composite" plugin for running all framework tests at a glance

Description

Hopefully with an accepted version of our fix for "cumulative expect" #226 at https://github.com/jquery/qunit/issues/226 it should be possible to stay in step easily with jquery's trunk version of qunit. In addition there is a helpful plugin "composite" which will enable us to make sure all framework tests are running with one operation rather than our currently opportunistic behaviour on checkin.

Further possible improvements:

• "grunt" task to automate running the "composite" test frame, as well as linting of all files using jshint
• harmonisation with GPII's version of jqunit, which has a slightly streamlined API avoiding the "new" style and the unidiomatic term "TestCase" which is more familiarly named "module" in qunit's terminology

Comments

• Colin Clark commented 2012-08-17T18:25:54.888-0400

  Reviewed, tested, and pushed. https://github.com/fluid-project/infusion/commit/095e1f1cde2c5d166e91b1ccaa18fd4c58967ebc

  I'd recommend that prior to closing this issue, we create a wiki page describing the new all tests feature and how to maintain it.

  colinclark: Bosmon: This all-tests.html file scares me quite a bit
  [5:48pm] colinclark: I assume it has to be updated with the addition of each new test file?
  [5:48pm] Bosmon: colinclark - because it includes an HTML comment with an embedded piece of shell scripting? : P
  [5:48pm] Bosmon: Yes, right now it does
  [5:49pm] Bosmon: I should have put a "TODO" on it saying "implement this in grunt once we start using it"
  [5:49pm] colinclark: yes
  [5:49pm] Bosmon: I was thinking about just this issue in today's SHOWER TIME
  [5:49pm] colinclark: i'll do that when i get back, perhaps
  [5:49pm] Bosmon: Start us on GRUNT?
  [5:49pm] colinclark: yes
  [5:49pm] Bosmon: THat would be awesome
  [5:49pm] colinclark: What is the blob of commented shell script?
  [5:49pm] colinclark: it looks like the hint of something that will find tests automatically
  [5:49pm] colinclark: but clearly it is not
  [5:50pm] Bosmon: It is the script which automatically generates the block of configuration containing the test files
  [5:50pm] Bosmon: Why is it clearly not?
  [5:50pm] Bosmon: I mean, it is not "automatic"...
  [5:50pm] EricDalquist left the chat room. (Quit: Leaving.)
  [5:50pm] Bosmon: Since you have to paste it into the command line yourself : P
  [5:50pm] Bosmon: But it is better than a poke in the eye
  [5:50pm] colinclark: ugh
  [5:51pm] colinclark: I might have made a wiki page
  [5:51pm] Bosmon: It seems you are not unconditionally prepared to accept that it may be better than a poke in the eye : P
  [5:51pm] alexn left the chat room. (Quit: Leaving.)
  [5:51pm] Bosmon: What would be on the wiki page?
  [5:52pm] colinclark: A description of how to run tests all at once
  [5:52pm] colinclark: how it works
  [5:52pm] colinclark: and how to update the page with new tests
  [5:52pm] Bosmon: Ah yes

• Justin Obara commented 2014-03-03T12:49:09.113-0500

  There is a separate jira for writing the documentation: FLUID-4774