Skip to content
Commits on Dec 28, 2011
  1. ie7 compatibility

    committed Dec 28, 2011
  2. redesign of qunit css

    committed Dec 28, 2011
Commits on Dec 8, 2011
  1. @jzaefferer

    Merge pull request #181 from simonz/development

    following issue #180, escape test names and show stack trace when failed
    jzaefferer committed Dec 8, 2011
  2. @simonz

    Escaping test names

    simonz committed Dec 8, 2011
  3. @simonz
Commits on Nov 24, 2011
  1. @jzaefferer

    Bump post-release version

    jzaefferer committed Nov 24, 2011
  2. @jzaefferer

    Release v1.2.0

    jzaefferer committed Nov 24, 2011
Commits on Nov 6, 2011
  1. @mikesherov
Commits on Nov 5, 2011
  1. @prathe
Commits on Nov 1, 2011
  1. @domenic

    Allow objects with no prototype to tested against object literals.

    I often use objects created with `Object.create(null)` as dictionaries, since then they don't have pre-filled dictionary entries for e.g. `constructor`, `hasOwnProperty`, `isPrototypeOf`, etc. However, in my tests, it is quite useful to test the dictionaries I create against object literals (which have `Object.prototype` as their prototype).
    
    This patch makes an exemption to the rule that two objects must have the same constructor, for the case where one has `null` prototype and the other `Object.prototype` as its prototype.
    domenic committed Nov 1, 2011
Commits on Oct 19, 2011
  1. Fix IE8 "Member not found" error

    Setting window.constructor causes this error in IE8, which happens when QUnit
    extends window.
    Jimmy Mabey committed Oct 19, 2011
  2. @hashar

    Using node-qunit port, the start/stop function are not exposed so we …

    …need to prefix any call to them with 'QUnit'. Aka: start() -> QUnit.start()
    hashar committed Oct 19, 2011
Commits on Oct 12, 2011
  1. @jzaefferer

    Remove the 'let teardown clean up globals test' - IE<9 doesn't suppor…

    …t (==buggy) deleting window properties, and that's not worth the trouble, as everything else passes just fine. Fixes #155
    jzaefferer committed Oct 12, 2011
  2. @jzaefferer
  3. @jzaefferer
Commits on Oct 11, 2011
  1. @jzaefferer
  2. @jzaefferer

    Bump post-release version

    jzaefferer committed Oct 11, 2011
  3. @jzaefferer

    Release 1.1.0

    jzaefferer committed Oct 11, 2011
  4. @jzaefferer

    Fixes #134 - Add a window.onerror handler. Makes uncaught errors actu…

    …ally fail the testsuite, instead of going by unnoticed.
    jzaefferer committed Oct 11, 2011
  5. @jzaefferer

    Whitespace cleanup

    jzaefferer committed Oct 11, 2011
Commits on Oct 10, 2011
  1. @jzaefferer

    Merge remote branch 'trevorparscal/master'

    Conflicts:
    	qunit/qunit.js
    jzaefferer committed Oct 10, 2011
  2. @trevorparscal

    Fixed IE compatibility issues with using toString on NodeList objects,

    which in some browsers results in [object Object] rather than [object
    NodeList]. Now using duck typing for NodeList objects based on the
    presence of length, length being a number, presence of item method
    (which will be typeof string in IE and function in others, so we just
    check that it's not undefined) and that item(0) returns the same value
    as [0], unless it's empty, in which case item(0) will return 0, while
    [0] would return undefined. Tested in IE6, IE8, Firefox 6, Safari 5 and
    Chrome 16.
    trevorparscal committed Oct 10, 2011
  3. @jzaefferer
  4. @jzaefferer
  5. @jzaefferer
  6. @jzaefferer
  7. @jzaefferer
  8. @jzaefferer
  9. @jzaefferer

    Merge remote branch 'wwalser/recursionBug'

    Conflicts:
    	qunit/qunit.js
    jzaefferer committed Oct 10, 2011
  10. @jzaefferer
  11. @jzaefferer

    Whitespace cleanup

    jzaefferer committed Oct 10, 2011
  12. @jzaefferer
  13. @jzaefferer
Commits on Oct 7, 2011
  1. @trevorparscal

    Using === instead of ==

    This doesn't have any functional difference because we are comparing a
    string literal with the results of Object.toString(), but it's better
    to be sure that they are the same type.
    trevorparscal committed Oct 7, 2011
  2. @trevorparscal

    Added more strict array type detection for dump output, and allowed N…

    …odeList objects to be output as arrays
    
    This helps prevent treating any object with a length property as an
    array, while maintaining the ability to render NodeList objects as
    arrays. jsDump output tests still pass after this patch is applied.
    trevorparscal committed Oct 7, 2011
Something went wrong with that request. Please try again.