Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

language fixes, typo #162

Open
wants to merge 1 commit into from

1 participant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Mar 9, 2012
  1. @Erkan-Yilmaz

    language fixes, typo

    Erkan-Yilmaz authored
This page is out of date. Refresh to see the latest.
Showing with 9 additions and 9 deletions.
  1. +5 −5 docs/index.html
  2. +4 −4 docs/index.md
View
10 docs/index.html
@@ -45,14 +45,14 @@
assert.equal(6, 'foobar'.length);
};</code></pre><p>Alternatively for large numbers of tests you may want to
export your own object containing the tests, however this
-is essentially the as above:</p><pre><code>module.exports = {
+is essentially the same as above:</p><pre><code>module.exports = {
'test String#length': function(beforeExit, assert) {
assert.equal(6, 'foobar'.length);
}
};</code></pre><p>If you prefer not to use quoted keys:</p><pre><code>exports.testsStringLength = function(beforeExit, assert) {
assert.equal(6, 'foobar'.length);
};</code></pre><p>The argument passed to each callback is <code>beforeExit</code> and <code>assert</code>.
-The context ("<code>this</code>") of each test function is a <em>Test</em> object. You can pass a function to <code>beforeExit</code> to make sure the assertions are run before the tests exit. This is can be used to verify that tests have indeed been run. <code>beforeExit</code> is a shortcut for listening to the <code>exit</code> event on <code>this</code>. The second parameter <code>assert</code> is the <code>assert</code> object localized to that test. It makes sure that assertions in asynchronous callbacks are associated with the correct test.</p><pre><code>exports.testAsync = function(beforeExit, assert) {
+The context ("<code>this</code>") of each test function is a <em>Test</em> object. You can pass a function to <code>beforeExit</code> to make sure the assertions are run before the tests exit. This can be used to verify that tests have indeed been run. <code>beforeExit</code> is a shortcut for listening to the <code>exit</code> event on <code>this</code>. The second parameter <code>assert</code> is the <code>assert</code> object localized to that test. It makes sure that assertions in asynchronous callbacks are associated with the correct test.</p><pre><code>exports.testAsync = function(beforeExit, assert) {
var n = 0;
setTimeout(function() {
++n;
@@ -81,7 +81,7 @@
comparisons, opposed to <code>assert.equal()</code> which uses <code>==</code>.</p><pre><code>assert.eql('foo', 'foo');
assert.eql([1,2], [1,2]);
assert.eql({ foo: 'bar' }, { foo: 'bar' });</code></pre><h3 id="assert-includes-obj-val-msg">assert.includes(obj, val[, msg])</h3><p>Assert that <code>obj</code> is within <code>val</code>. This method supports <code>Array</code>s
-and <code>Strings</code>s.</p><pre><code>assert.includes([1,2,3], 3);
+and <code>String</code>s.</p><pre><code>assert.includes([1,2,3], 3);
assert.includes('foobar', 'foo');
assert.includes('foobar', 'bar');</code></pre><h3 id="assert-response-server-req-res-fn-msg-fn">assert.response(server, req, res|fn[, msg|fn])</h3><p>Performs assertions on the given <code>server</code>, which should <em>not</em> call
<code>listen()</code>, as this is handled internally by expresso and the server
@@ -137,7 +137,7 @@
so the following is equivalent to the command above:</p><pre><code>$ expresso</code></pre><p>If you wish to unshift a path to <code>require.paths</code> before
running tests, you may use the <code>-I</code> or <code>--include</code> flag.</p><pre><code>$ expresso --include lib test/*</code></pre><p>The previous example is typically what I would recommend, since expresso
supports test coverage via <a href="http://github.com/visionmedia/node-jscoverage">node-jscoverage</a> (bundled with expresso),
-so you will need to expose an instrumented version of you library.</p><p>To instrument your library, simply run <a href="http://github.com/visionmedia/node-jscoverage">node-jscoverage</a>,
+so you will need to expose an instrumented version of your library.</p><p>To instrument your library, simply run <a href="http://github.com/visionmedia/node-jscoverage">node-jscoverage</a>,
passing the <em>src</em> and <em>dest</em> directories:</p><pre><code>$ node-jscoverage lib lib-cov</code></pre><p>Now we can run our tests again, using the <em>lib-cov</em> directory that has been
instrumented with coverage statements:</p><pre><code>$ expresso -I lib-cov test/*</code></pre><p>The output will look similar to below, depending on your test coverage of course :)</p><p><img alt="node coverage" src="http://dl.dropbox.com/u/6396913/cov.png" /></p><p>To make this process easier expresso has the <code>-c</code> or <code>--cov</code> which essentially
does the same as the two commands above. The following two commands will
@@ -171,4 +171,4 @@
}, 100);</code></pre><p>Note that you only have one "shot" at exporting. You have to export all of your test functions in the same loop as the first one. That means you can't progressively add more test functions to the <code>exports</code> object.</p></html>
</div>
</body>
-</html>
+</html>
View
8 docs/index.md
@@ -43,7 +43,7 @@ To define tests we simply export several functions:
Alternatively for large numbers of tests you may want to
export your own object containing the tests, however this
-is essentially the as above:
+is essentially the same as above:
module.exports = {
'test String#length': function(beforeExit, assert) {
@@ -58,7 +58,7 @@ If you prefer not to use quoted keys:
};
The argument passed to each callback is `beforeExit` and `assert`.
-The context ("`this`") of each test function is a _Test_ object. You can pass a function to `beforeExit` to make sure the assertions are run before the tests exit. This is can be used to verify that tests have indeed been run. `beforeExit` is a shortcut for listening to the `exit` event on `this`. The second parameter `assert` is the `assert` object localized to that test. It makes sure that assertions in asynchronous callbacks are associated with the correct test.
+The context ("`this`") of each test function is a _Test_ object. You can pass a function to `beforeExit` to make sure the assertions are run before the tests exit. This can be used to verify that tests have indeed been run. `beforeExit` is a shortcut for listening to the `exit` event on `this`. The second parameter `assert` is the `assert` object localized to that test. It makes sure that assertions in asynchronous callbacks are associated with the correct test.
exports.testAsync = function(beforeExit, assert) {
var n = 0;
@@ -143,7 +143,7 @@ comparisons, opposed to `assert.equal()` which uses `==`.
### assert.includes(obj, val[, msg])
Assert that `obj` is within `val`. This method supports `Array`s
-and `Strings`s.
+and `String`s.
assert.includes([1,2,3], 3);
assert.includes('foobar', 'foo');
@@ -260,7 +260,7 @@ running tests, you may use the `-I` or `--include` flag.
The previous example is typically what I would recommend, since expresso
supports test coverage via [node-jscoverage](http://github.com/visionmedia/node-jscoverage) (bundled with expresso),
-so you will need to expose an instrumented version of you library.
+so you will need to expose an instrumented version of your library.
To instrument your library, simply run [node-jscoverage](http://github.com/visionmedia/node-jscoverage),
passing the _src_ and _dest_ directories:
Something went wrong with that request. Please try again.