I once tried to write that all framework runner.
I wrote an abstraction that fit over the currently popular test frameworks.
then people wrote new frameworks so it didn't fit anymore.
the universal test runner is the author sets "scripts": { "test":
"node test/index.js" } (or whatever)
and then you go `npm test`
if it exists non 0, the test failed. it's the framework's (if there is
one) to produce useful output.
this even works when a test is a bash script or something.
On Tue, Jul 17, 2012 at 10:13 PM, Alex Young <[email protected]> wrote:
> The CommonJS test module uses those export-based tests, and somehow I've
> been assuming this is the 'right' way to write tests. It seems like there
> are three options:
>
> * CommonJS unit testing module style
> * Mocha (and similar) where a program is used to execute the test because it
> contains top-level functions without relying on a require
> * A plain old Node script
>
> On Tuesday, July 17, 2012 9:49:41 AM UTC+1, jesusabdullah wrote:
>>
>> > There's no test runner for all frameworks.
>>
>> I use one that's pretty sweet, it's called `node`. ;)
>>
>> (nevermind that vows tests usually export instead of run.)
>>
>> --Josh
>>
>> On Tue, Jul 17, 2012 at 1:44 AM, Nuno Job <[email protected]> wrote:
>> > There's no test runner for all frameworks.
>> >
>> > That would be a great idea though but it's very unlikely that someone
>> > reaches a compromise between features that is acceptable for different
>> > test
>> > framework developers.
>> >
>> > Nuno
>> >
>> >
>> > On Tue, Jul 17, 2012 at 2:43 AM, Dominic Tarr <[email protected]>
>> > wrote:
>> >>
>> >> _everyone_ a strong opinion on this.
>> >>
>> >> our test frameworks need to be rewritten now that we have domains.
>> >>
>> >> maybe, write through exercises in the book?
>> >>
>> >> On Tue, Jul 17, 2012 at 8:32 AM, Roly Fentanes <[email protected]>
>> >> wrote:
>> >> > If you can get your tests' point across clearly by using node's
>> >> > `assert`
>> >> > module and it's not that much difficult to structure compared to a
>> >> > full
>> >> > featured test framework, then consider using it.
>> >> >
>> >> > Otherwise, mocha is the popular recent one, and my personal choice.
>> >> > nodeunit
>> >> > is easy to understand too, and has been around for a while. vows used
>> >> > to
>> >> > be
>> >> > the choice, there's still a lot of popular modules with their tests
>> >> > written
>> >> > with vows. But it's no longer maintained and it shows.
>> >> >
>> >> > chai is often used along with these to make assertions easier to
>> >> > understand.
>> >> >
>> >> >
>> >> > On Monday, July 16, 2012 9:56:14 AM UTC-7, Alex Young wrote:
>> >> >>
>> >> >> Hello,
>> >> >>
>> >> >> I write about Node a lot, and I often illustrate concepts using
>> >> >> tests.
>> >> >> However, there isn't a standard test runner for Node.
>> >> >>
>> >> >> So, let's say I'm writing a book about Node. I'd like to include
>> >> >> examples
>> >> >> using a test runner that's idiomatic, lightweight, and likely to be
>> >> >> around
>> >> >> in a year or two. I'm thinking Mocha or Nodeunit might be a good
>> >> >> idea.
>> >> >>
>> >> >> My projects from 2010-2011 seemed to use Nodeunit, and I've switched
>> >> >> a
>> >> >> few
>> >> >> to Mocha with very little trouble. Their APIs aren't directly
>> >> >> compatible
>> >> >> but the same concepts can be readily gleaned in both.
>> >> >>
>> >> >> Does anyone have any strong opinions about this? What test runner
>> >> >> would
>> >> >> you expect (or want) to see in books about Node?
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Alex
>> >> >
>> >> > --
>> >> > Job Board: http://jobs.nodejs.org/
>> >> > Posting guidelines:
>> >> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> >> > You received this message because you are subscribed to the Google
>> >> > Groups "nodejs" group.
>> >> > To post to this group, send email to [email protected]
>> >> > To unsubscribe from this group, send email to
>> >> > [email protected]
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/nodejs?hl=en?hl=en
>> >>
>> >> --
>> >> Job Board: http://jobs.nodejs.org/
>> >> Posting guidelines:
>> >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> >> You received this message because you are subscribed to the Google
>> >> Groups "nodejs" group.
>> >> To post to this group, send email to [email protected]
>> >> To unsubscribe from this group, send email to
>> >> [email protected]
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/nodejs?hl=en?hl=en
>> >
>> >
>> > --
>> > Job Board: http://jobs.nodejs.org/
>> > Posting guidelines:
>> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> > You received this message because you are subscribed to the Google
>> > Groups "nodejs" group.
>> > To post to this group, send email to [email protected]
>> > To unsubscribe from this group, send email to
>> > [email protected]
>> > For more options, visit this group at
>> > http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>>
>>
>> --
>> Joshua Holbrook
>> Head of Support
>> Nodejitsu Inc.
>> [email protected]
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
