Permalink
Commits on Nov 25, 2011
  1. [dist] Version bump. 0.6.0

    indexzero committed Nov 25, 2011
  2. event order for 'on'

    now if you have a nested 'on' declaration I will enforce the nested order.
    seebees committed with indexzero Nov 20, 2011
  3. [v0.6 fix] Properly inspect errors

    This is related and blocked by cloudhead/eyes.js#12.
    
    Gist of what's going on: `Error` properties are non-enumerable in `node
    v0.6`, so `Object.keys` which is being used in `eyes.js` won't list them
    (we need to use `Object.getOwnPropertyNames`). This results in errors
    being outputted as `{}`, for example in `assert.isNull(err)` statement.
    mmalecki committed with indexzero Nov 8, 2011
  4. When an uncaught exception is caught in watch mode, print it in the c…

    …onsole and continue watch.
    juggy committed with indexzero Sep 14, 2011
  5. When called outside the vows context where `this.stack` && `source` a…

    …re undefined it will now no longer crash and burn
    Raynos committed with indexzero Aug 30, 2011
  6. Add support for asynchronous teardowns.

    Daniel Brockman committed with indexzero Apr 30, 2011
  7. Edited README.md via GitHub

    JerrySievert committed with indexzero Aug 21, 2011
  8. events other then success

    1. added .isEvent property (to distinguish between legacy 'success' and any sub-events)
    2. added property .event that is either 'success' or the named sub-event
    3. the api for sub-events is a context named either 'on' or 'events' ('events' is transformed into 'on')
    
    1. updated addVow to look at the vow.binding.context.event instead of 'success'
    2. if the sub-event is 'error' there is no need to listen for the topics error event again
    3. Hooked EventEmitter.prototype.emit so I can capture events that happen before addVow is run.
    4. Updated the vow calling params so if we have a known emitted event I don't change the calling structure (i.e. add a null error)
    
    1. Throw if a sub-event or 'on' context has a topic
    2. Sub-events can inherit from EventEmitter
    3. changed 'success' to ctx.event
    4. execute new context even if the event has already fired
    
    Added basic tests to demonstrate "Vows with sub events"
    
    Fixes #109
    seebees committed with indexzero Nov 20, 2011
Commits on Nov 2, 2011
  1. [dist] Version bump. 0.5.13

    indexzero committed Nov 2, 2011
Commits on Oct 24, 2011
  1. Merge pull request #146 from mmalecki/fix-output

    [fix] Fix failed assertions output
    indexzero committed Oct 24, 2011
  2. [fix] Fix failed assertions output

    Latest changes made to Vows in order to make it compatible with `node
    v0.5.x` (see issue #141) introduce a bug which caused Vows to output
    only file name and line when assertion fails:
    
        when testing
          ✗ should output details
            »  // test.js:8
    
    This turned out to be a really small bug. Output works now:
    
        when testing
          ✗ should output details
            » expected { a: 1, b: 3 },
              got      { a: 1, b: 2 } (deepEqual) // test.js:8
    
    Sorry for that.
    mmalecki committed Oct 24, 2011
Commits on Oct 22, 2011
  1. [dist] Version bump. 0.5.12

    indexzero committed Oct 22, 2011
Commits on Oct 15, 2011
Commits on Oct 14, 2011
  1. [test v0.6] Make `assert-test.js` v0.6-compatible

    Since nodejs/node-v0.x-archive@8c8d518, `assert` module is a function. When you look
    at lib/vows/suite.js:126, it checks if topic is a function and then, if
    it is, it executes it and passes results down to vows. Of course, it
    fails hard in this case, since `assert` module is a function (resulting
    in error without a stack trace).
    mmalecki committed Oct 14, 2011
Commits on Oct 13, 2011
  1. [v0.6] Handle stdout suppressing correctly

    In node v0.5.x `process.stdout` is a getter, so assigning to it makes
    no difference (see nodejs/node-v0.x-archive#1878 - thanks @bnoordhuis).
    mmalecki committed Oct 13, 2011
Commits on Oct 12, 2011
  1. [api] Rename `assert.length` to `assert.lengthOf`

    This change is caused by nodejs/node-v0.x-archive@8c8d518 (sorry!). This commit made
    `assert` module behave like `assert.ok` function, thus (since JavaScript
    functions have length), `assert.length == assert.ok.length`. Because of
    that, assigning `assert.length` wouldn't change anything (function
    properties are freezed).
    
    This is a major API break.
    mmalecki committed Oct 12, 2011
Commits on Oct 11, 2011