* Survey::responseJSON mutator was not doing the right thing when
responseId argument was passed in
* www_viewGradeBook template fixes and documentation
Tests are defined via a JSON-encoded spec, through Web Crud interface
Test results are TAP encoded, and TAP parsed and prettified into HTML
Added i18n, help and tests
Added survey feedback template and method for returning the templated feedback for a given response
Used this to clean up the default survey template, and updated the i18n and help
refactored out repetitive checking of takenCount
added i18n template variables to Survey template so that user is told what happened for timeouts etc..
before you apply strictures (use strict, use warnings, etc.)
Add calls to use strict to each Help module. This is probably
an overstrict interpretation of the rule.
Collaboration template labels need to be rethought
fix t/i18n/label.t to not always check on the name of a variable as an i18n entry,
since the description may hold the actual variable description.