Find file
Fetching contributors…
Cannot retrieve contributors at this time
151 lines (125 sloc) 5.6 KB
<!DOCTYPE html>
<html lang="en">
<meta charset="utf-8" />
<title>node-async-testing &mdash; simple intuitive testing for node.js</title>
<link rel="stylesheet" href="assets/style.css">
<link rel="icon" href="favicon.ico">
<div id="container">
<header id="main-header">
<h2>Simple, intuitive testing for node.js</h2>
<li class="current"><a href="./">Home</a></li>
<li><a href="writing-tests.html">Writing Tests</a></li>
<li><a href="running-tests.html">Running Tests</a></li>
<section id="intro">
<b>node-async-testing</b> is a fast, extendable uniting testing module for
<a href="">Node.js</a>. It...
<li>fully embraces Node's async environment</li>
<li>supports parallel test and suite execution</li>
<li>has true test and suite setup and teardown functions</li>
helps your organize your suites by allowing you to group different
tests together in sub-suites
<li>allows you to easily add your own custom assertion methods</li>
<li>let's you customize test output for your particular needs</li>
<h2>Page outline:</h2>
<li><a href="#opinions">node-async-testing's opinions</a></li>
<li><a href="#installing">Installing</a></li>
<li><a href="#contact">Getting the source, Getting involved and Getting in touch</a></li>
<li><a href="#getting-started">Where to start</a></li>
<section id="opinions">
<h1><b>node-async-testing's</b> <del>biases</del> opinions:</h1>
<h2>Node is asynchronous, so testing should be too</h2>
This applies to everything: assertions, errors, callbacks, setup, teardown,
reports, and so on.
<h2>You should be able to run tests in parallel or serially</h2>
Running tests in parallel is much faster, but makes it impossible to
accurately deal with errors.
<h2>You should be able to test any code, and all aspects of it</h2>
<p>Make no assumptions about the code being tested.</p>
<h2>You shouldn't have to learn new assertion functions</h2>
The assertion module that comes with Node is great. If you are familiar with
it you won't have any problems, so no need to learn new functions (though
you can add your own if you want).
<h2>No specifications, and no natural language suites</h2>
Not another Behavior Driven Development testing framework. I don't like
specifications and what not. They only add verbosity. <code>"Text X"</code> followed
by a function is just right.
<h2>Test files should be executable by Node</h2>
No preprocessors or custom scripts. If your test file is called
<code>my_test_file.js</code> then <code>node my_test_file.js</code> should run it.
<section id="installing">
<p>With npm:</p>
<div class="highlight"><pre>npm install async_testing</pre></div>
<p>By hand:</p>
<div class="highlight"><pre>
mkdir -p ~/.node_libraries
<span class="nb">cd</span> ~/.node_libraries
git clone --recursive git:// async_testing</pre></div>
<section id="contact">
<h1>Getting the source, Getting involved and Getting in touch:</h1>
The source code for <b>node-async-testing</b> is
<a href="">located on GitHub</a>.
Feel free to send me pull requests, or
<a href="">report any issues you find</a>.
If you are looking for something to do, I maintain
<a href="">a list</a> of things that
need to be done or things I am thinking about doing.
To get in contact with me directly, you can send me a message on GitHub or
<a href="">send me an email</a>. Sometimes I can be
an awful correspondent, so don't take it personally. My best friends get the same treatment.
I will eventually get back to you, just sometimes it can take months. A little
prodding every now and then can't hurt.
<section id="getting-started">
<h1>Where to start:</h1>
Read about <a href="writing-tests.html">writing tests and suites</a> or
<a href="running-tests.html">how to run your suites</a>.
Check out <a href="">the examples</a>.
I recommend looking at <a href="">test/test-overview.js</a> first.
<p>Watch this brief screencast:</p>
<video id="demo" width="808" height="540" controls preload>
<source src="" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"'>