Commits on Sep 4, 2010
  1. Add disclaimer about browser support for the web runner

    Benjamin Thomas committed Sep 4, 2010
  2. Handle errors in test files, updated README

    Benjamin Thomas committed Sep 4, 2010
Commits on Sep 3, 2010
  1. Update web runner to update UI when test files are changed.

    Web site will now sure the current tests. Even if you add remove tests.
    It already would run the most up to date tests, but now it properly
    shows what it is doing.
    Benjamin Thomas committed Sep 3, 2010
  2. Rename default runner and change runSuites to only run files.

    Change the default runner to something more descriptive.  We'll still
    know it is the default in our hearts though.
    Changing runSuites to only run files/directories (and renaming it
    runFiles) is a much bigger change.  If you want to run a specific
    suite object, just call runSuite directly with the object.
    Runners can now assume that all items are files or directories.
    Benjamin Thomas committed Sep 3, 2010
Commits on Sep 2, 2010
  1. Make sure we can terminate before terminating

    Benjamin Thomas committed Sep 2, 2010
  2. Fix inproperly labelled assertions.

    Benjamin Thomas committed Sep 2, 2010
  3. Initial version of new 'web' test runner.

    The 'web' test runner will start a web server and when you go to the site
    you can run the test suites from there.  Each time you run the suites it
    reloads all files from source, so you can leave the web page open and
    edit and then test and then edit and then test and so on...
    Still need documentation and better command line support for launching.
    Currently no way to run it without hard coding that you want to use that
    Has and node-webworker as two new dependencies. Haven't
    figured out how to bundle the appropriate client code yet.
    Benjamin Thomas committed Sep 2, 2010
Commits on Sep 1, 2010
  1. A few small changes, white-space, organization, etc

    Benjamin Thomas committed Sep 1, 2010
Commits on Aug 11, 2010
Commits on Aug 10, 2010
  1. Update README some more

    Benjamin Thomas committed Aug 10, 2010
  2. Fix issue where tests that were run in parallel would be many nested

    functions deep.
    Benjamin Thomas committed Aug 10, 2010
  3. Update default test runner. Change output behavior some

    Benjamin Thomas committed Aug 10, 2010
Commits on Aug 9, 2010
  1. Update authors file

    Benjamin Thomas committed Aug 9, 2010
  2. Merge branch 'rewrite' into master

    This was a complete rewriting of node-async-testing from the ground up.
    Pretty much everything about node-async-testing has changed. But I hope
    you will agree that I have kept the same spirit of the first version and
    have even better addressed the goals listed in the README.
    New changes:
    + Tests can be run in parallel to have them run very quickly.  The
    default is still to have each test run consecutively one after another
    for the most accurate results.
    + No more do we try and guess if a test is synchronous. I got bit by
    that too many times when I changed a test to be asynchronous but forgot
    to update the arguments.
    + The suite runner is now much more robust, it can take modules, file
    names, directory names or some combination there of.
    + When running individual test files from the command line it is now
    easy to pass in arguments to change the output or the behaivor.  For
    example, it is now trivially easy to run one specific test in a suite.
    + Colored output. I'm quite excited about this, but I suppose I should
    add an option to disable it.
    + It is now possible to easily write your own test runners and to format
    the results however you'd like.
    Things that are now a bit more work:
    + We now assume that the default use case is to have one test suite per
    file.  It is still easy to have more than one test suite in a file but
    we have no examples of it. Unfortunately, however if you have more than
    one suite it a file your suites don't get to have names.  As
    node-async-testing gets the name of a suite from the file it is in. I'd
    be interested in hearing suggestions for how to set a name in a suite in
    a way that doesn't feel tacked on. Even though I am talking about
    tacking this on...  :)
    + Setup/teardown functions are not nearly as straight-forward. I felt
    that an even simpler and easier system for writing tests out-weighed the
    convenience of the previous setup/teardown functions.  Now you have to
    write your setup/teardown functions as a wrapper function which take a
    test and return a new test.  No functionallity has been lost, it just
    isn't as convenient.
    Benjamin Thomas committed Aug 9, 2010
  3. Address the issue of setup/teardown functions.

    Benjamin Thomas committed Aug 9, 2010
  4. More documenting changes. You'd think I'd learn to do these all in on…

    …e commit
    Benjamin Thomas committed Aug 9, 2010
  5. Update README and documentation

    Benjamin Thomas committed Aug 9, 2010
  6. Fix require path issue from moving node-async-test command

    Benjamin Thomas committed Aug 9, 2010
  7. Small code changes. Biggest being rename `test.finished` to `test.fin…

    Other than that just clean up the code in a couple spots.
    Benjamin Thomas committed Aug 9, 2010
  8. add package.json file

    Benjamin Thomas committed Aug 9, 2010
  9. add ifError method to assert module wrapping

    Benjamin Thomas committed Aug 9, 2010
  10. Basically, document and clean up the new version a bit. Both the code…

    … and the workflow.
    Benjamin Thomas committed Aug 9, 2010
Commits on Jul 9, 2010
  1. added ifError method for assert module

    clement committed with Benjamin Thomas Jul 6, 2010
Commits on Jun 18, 2010
  1. Update api.markdown again

    Benjamin Thomas committed Jun 18, 2010
  2. Try out replacing the current dir with '.' in log level 1 in the defa…

    …ult test runner.
    Benjamin Thomas committed Jun 18, 2010
  3. Update api.markdown slightly.

    Benjamin Thomas committed Jun 18, 2010
  4. Addressed the rest of the issues in todo.txt.

    + Exit status codes.  `node-async-testing` will now exit with the number
      of tests that failed.
    + If a test doesn't finish, mention that on exit.  Added a new event,
    + Cleanup misorganized code: testResults function.  Done.
    + In runSuites, if can't find a file, print warning, don't error.  Done.
    + Decide if the distinction between errors and failures useful.
      Yes. I find it useful at least.
    + Decide if we should require all tests to call the finished function?
      Yes. I can't tell you how often I switch a function from synchronous
      to asynchronous and used to forget to add the `finished` function to
      the function parameters.  No more!
    Benjamin Thomas committed Jun 18, 2010
Commits on Jun 15, 2010
Commits on Jun 14, 2010
  1. A ton more changes. Now have a colored test runner using callbacks fr…

    …om the runSuites method.
    Still a few bugs.  And that whole cleaning up and simplifying thing kind
    of went out the window. But I added a lot of cool new features!  Will
    have to clean up next, again, I guess.
    Benjamin Thomas committed Jun 14, 2010
  2. Add LICENSE and AUTHORS file

    Benjamin Thomas committed Jun 14, 2010
  3. A complete rewrite of node-async-testing. Tests can now be run serial…

    …ly or in parallel.
    The old version of node-async-testing had kind of been hacked together
    quickly, and as its goals changed, the code base did its best to morph
    itself to handle the new situations.  Unfortunately, this meant that at
    its core, node-async-testing was written for one testing paradigm (no
    suites) but was rewritten to handle another (suites).
    I decided that cleaning it up was in order.  So, this is that attempt.
    As to how successful I was at 'cleaning it up', I'm not sure.  However,
    this does bring a major new feature!
    Tests can now be run either serially or in parallel:
    + If tests are run serially (the default, and basically the same as it
      works now), then errors are caught and properly associated with their
    + If tests are run in parallel, then they are all started at the same
      time.  This is much, much faster and very cool.  node-async-testing
      will then do its best to figure out which errors (assertions still
      work just fine) are with which tests by looking at which tests are
      still running when an error happens and then narrowing down from
    At this point the rewrite isn't usable as it doesn't really report the
    results of the tests. Yet.  But that will come next.  I'm working on
    adding some ideas from -- primarily,
    the colored output and the fantastic API for building test runners.
    Also, the setup and teardown functionallity has not been readded to the
    rewrite. I am considering going with nodeunit's approach to that by just
    making you wrap your test functions in your own setup/teardown
    functions.  Simplifies things a lot!
    See `test/test-everything.js` for a (very rough) example of how things
    are looking.
    Feedback much appreciated!
    (`node-async-test`, `README.markdown` and the files in `examples`
    have not been updated.)
    Benjamin Thomas committed Jun 14, 2010
Commits on Jun 3, 2010
  1. Move node-async-test functions to async_testing.js

    I've moved most of the code from node-async-test into the
    runSuitesInPaths method in async_testing.js.  This greatly
    simplifies node-async-test and allows me to write a
    "test/all.js" file with a single line (aside from requires):
    We may want to think about combining the runSuitesInPaths utility
    in with runSuites at some point.  It would be neat if runSuites
    could act on dirs or filenames or modules.
    gsf committed with Benjamin Thomas Apr 18, 2010
Commits on Mar 23, 2010
  1. Replaced "excited" with "exited"

    gsf committed with Benjamin Thomas Mar 22, 2010