Skip to content
Browse files

More broken links

  • Loading branch information...
1 parent 21d1faf commit d151865677461d73a669af88631c35b71ccaa834 Christian Johansen committed Feb 7, 2012
View
0 ...es/buster-test/xunit-console-reporter.png → public/images/buster-test/dots-reporter.png
File renamed without changes
View
0 ...ages/buster-test/bdd-console-reporter.png → ...r-test/specification-console-reporter.png
File renamed without changes
View
5 site/docs/args.html
@@ -334,9 +334,8 @@ <h3 id="validator-file-or-directory"><code>validators.fileOrDirectory("err")</co
});</code></pre>
<h3 id="async-validators">Asynchronous validators</h3>
<p>
- <a href="/docs/buster-promise/">Promises</a> are used to facilitate
- asynchronous validators. Here's an example of a validator that checks if a
- file is larger than 1MB.
+ Promises are used to facilitate asynchronous validators. Here's an example
+ of a validator that checks if a file is larger than 1MB.
</p>
<pre><code>var busterPromise = require("buster-promise");
opt.addValidator(function () {
View
4 site/docs/configuration.html
@@ -86,7 +86,7 @@ <h2 id="properties">Configuration properties</h2>
<code>browser</code> or <code>node</code>. The browser environment allows
you to run tests from the command-line and have them executed in one or
more browsers through the server component of Buster.JS. Refer to the
- <a href="/browser-testing/">browser testing page</a>.
+ <a href="/docs/browser-testing/">browser testing page</a>.
</dd>
<dt><code>env</code></dt>
<dd>
@@ -172,7 +172,7 @@ <h2 id="properties">Configuration properties</h2>
<dd>
Only applies to browser runs. When set to <code>false</code>, Buster will
not run tests immediately after loading all files.
- Refer to <a href="/starting-testrun-manually/">starting
+ Refer to <a href="/docs/starting-testrun-manually/">starting
test runs manually</a> for more information.
</dd>
<dt><code>extends</code></dt>
View
6 site/docs/getting-started.html
@@ -89,7 +89,7 @@
See the full <a href="/docs/test/test-case/">buster.testCase</a> docs
and <a href="/docs/assertions/">buster-assertions</a> docs for
details. There are also mocks and stubs and more, via
- the <a href="/sinon-buster/">sinon-buster</a> module.
+ the <a href="/docs/sinon/">sinon-buster</a> module.
</p>
<h2>Run tests</h2>
<p>When you have a config file, you're ready to run tests.</p>
@@ -100,7 +100,7 @@
test run of <a href="/docs/args/">buster-args</a>.
</p>
<p><img src="/images/node-testing/buster-test-node.png" width="633" height="382"></p>
-<p>See the <a href="/node-testing/">Node testing</a> documentation for more.</p>
+<p>See the <a href="/docs/node-testing/">Node testing</a> documentation for more.</p>
<h3>Browser tests</h3>
<p>First, start a server. Open a terminal and type in <kbd>buster server</kbd>.</p>
<p><img src="/images/overview/buster-server-start.png" width="633" height="382"></p>
@@ -111,7 +111,7 @@
<p><img src="/images/overview/buster-server-capture-firefox.png" width="827" height="339"></p>
<p>Then you're ready to run the tests with <kbd>buster test</kbd>.</p>
<p><img src="/images/overview/buster-test-run-browsers.png" width="633" height="382"></p>
-<p>See the <a href="/browser-testing/">browser testing</a> documentation for more.</p>
+<p>See the <a href="/docs/browser-testing/">browser testing</a> documentation for more.</p>
<h3>Hybrid tests</h3>
<p>
If your project has both Node and browser tests, and your config file
View
4 site/docs/index.html
@@ -17,11 +17,11 @@
and <a href="hybrid-testing/">hybrid Node and browser testing</a>.
</p>
<p>
- <a href="buster-test/test-case/">buster.testcase</a> documents contexts, setUp
+ <a href="/docs/test/test-case/">buster.testcase</a> documents contexts, setUp
and tearDown, asynchronous tests, and more.
</p>
<p>
- <a href="buster-assertions/">buster.assertions</a> documents all of our
+ <a href="/docs/assertions/">buster.assertions</a> documents all of our
assertions. There are lots of them.
</p>
<h2>Modules</h2>
View
2 site/docs/node-testing.html
@@ -40,7 +40,7 @@
<p>To run the tests, simply type:</p>
<p><kbd>buster test</kbd></p>
<p>
- Here's the test output for the <a href="/buster-args/">buster-args</a> module.
+ Here's the test output for the <a href="/docs/args/">buster-args</a> module.
</p>
<p><img src="/images/node-testing/buster-test-node.png" width="633" height="382"></p>
<p>
View
2 site/docs/sinon.html
@@ -4,7 +4,7 @@
</p>
<p>
Sinon specific assertions are documented
- at <a href="/buster-assertions/">buster-assertions</a>.
+ at <a href="/docs/assertions/">buster-assertions</a>.
</p>
<p>
Refer to <a href="http://sinonjs.org/docs/">the Sinon.JS documentation</a> and
View
6 site/docs/test/context.html
@@ -9,7 +9,7 @@
<p>
A test context is Buster's internal test case/specification data
format. Specifically, a test context is the kind of object that the
- <a href="/docs/test/test-runner/">test runner</a> knows how to run. This document
+ <a href="/docs/test/runner/">test runner</a> knows how to run. This document
describes the data format in detail - what features it and the runner supports
as well as how to create test contexts from external front-ends.
</p>
@@ -70,7 +70,7 @@ <h2 id="testContext"><code>testContext</code></h2>
<dt><code>contexts</code></dt>
<dd>
An array of <a href="#testContext"><code>testContext</code></a> objects. In other words, the test
- context data format (and thus, the <a href="/docs/test/test-runner/">test runner</a>)
+ context data format (and thus, the <a href="/docs/test/runner/">test runner</a>)
supports arbitrarily nested contexts.
</dd>
<dt><code>parent</code></dt>
@@ -114,7 +114,7 @@ <h2 id="test"><code>test</code></h2>
<h2 id="async">Asynchronous tests</h2>
<p>
There is no flag to mark tests as asynchronous even though the
- <a href="/docs/test/test-runner/">test runner</a> supports both synchronous and
+ <a href="/docs/test/runner/">test runner</a> supports both synchronous and
asynchronous tests. The reason is that it cannot be determined up-front if a
test is asynchronous or not.
</p>
View
42 site/docs/test/reporters.html
@@ -10,7 +10,7 @@
<dd><code>buster.reporters;</code></dd>
</dl>
<p>
- Reporters listen to <a href="/docs/test/test-runner/">test runner</a> events and
+ Reporters listen to <a href="/docs/test/runner/">test runner</a> events and
visualize progress and results of test runs. Buster ships with several
alternatives, and it is easy to <a href="#implement">make your own</a>.
</p>
@@ -46,7 +46,7 @@ <h2 id="dots"><code>dots</code></h2>
<p>
The <strong>A</strong> indicating an asynchronous test is replaced by one
of the others when the test completes, or a <strong>T</strong> if it times
- out (using <a href="en.wikipedia.org/wiki/ANSI_escape_code">ANSI escape characters</a>).
+ out (using <a href="http://en.wikipedia.org/wiki/ANSI_escape_code">ANSI escape characters</a>).
</p>
<p>
In order to help you find the source of errors faster, the reporter filters
@@ -60,7 +60,7 @@ <h3 id="dots-reporter-create" data-title="+create(options)+">
Create an instance.
</p>
<h3 id="dots-reporter-listen" data-title="+listen(testRunner)+">
- <code>listen(<a href="/docs/test/test-runner/">testRunner</a>)</code>
+ <code>listen(<a href="/docs/test/runner/">testRunner</a>)</code>
</h3>
<p>
Bind the reporter to a test runner.
@@ -69,10 +69,10 @@ <h3 id="dots-reporter-listen" data-title="+listen(testRunner)+">
var dotsReporter = require("buster-test").reporters.dots;
var reporter = dotsReporter.create({ color: false });
-var runner = testRunner.<a href="/docs/test/test-runner/#create">create</a>();
+var runner = testRunner.<a href="/docs/test/runner/#create">create</a>();
reporter.listen(runner);
-runner.<a href="/docs/test/test-runner/#runSuite">runSuite</a>(...);</code></pre>
+runner.<a href="/docs/test/runner/#runSuite">runSuite</a>(...);</code></pre>
<h3 id="dots-reporter-sample">Sample output</h3>
<p><img src="/images/buster-test/dots-reporter.png" width="661" height="698"></p>
</div>
@@ -98,7 +98,7 @@ <h3 id="specification-reporter-create" data-title="+create(options)+">
Create an instance.
</p>
<h3 id="specification-reporter-listen" data-title="+listen(testRunner)+">
- <code>listen(<a href="/docs/test/test-runner/">testRunner</a>)</code>
+ <code>listen(<a href="/docs/test/runner/">testRunner</a>)</code>
</h3>
<p>
Bind the reporter to a test runner.
@@ -107,10 +107,10 @@ <h3 id="specification-reporter-listen" data-title="+listen(testRunner)+">
var specificationReporter = require("buster-test").reporters.specification;
var reporter = specificationReporter.create({ color: false });
-var runner = testRunner.<a href="/docs/test/test-runner/#create">create</a>();
+var runner = testRunner.<a href="/docs/test/runner/#create">create</a>();
reporter.listen(runner);
-runner.<a href="/docs/test/test-runner/#runSuite">runSuite</a>(...);</code></pre>
+runner.<a href="/docs/test/runner/#runSuite">runSuite</a>(...);</code></pre>
<h3 id="specification-reporter-sample">Sample output</h3>
<p><img src="/images/buster-test/specification-reporter.png" width="685" height="681"></p>
</div>
@@ -126,7 +126,7 @@ <h3 id="quiet-reporter-create" data-title="+create(options)+">
Create an instance.
</p>
<h3 id="quiet-reporter-listen" data-title="+listen(testRunner)+">
- <code>listen(<a href="/docs/test/test-runner/">testRunner</a>)</code>
+ <code>listen(<a href="/docs/test/runner/">testRunner</a>)</code>
</h3>
<p>
Bind the reporter to a test runner.
@@ -135,10 +135,10 @@ <h3 id="quiet-reporter-listen" data-title="+listen(testRunner)+">
var quietReporter = require("buster-test").reporters.quiet;
var reporter = quietReporter.create({ color: false });
-var runner = testRunner.<a href="/docs/test/test-runner/#create">create</a>();
+var runner = testRunner.<a href="/docs/test/runner/#create">create</a>();
reporter.listen(runner);
-runner.<a href="/docs/test/test-runner/#runSuite">runSuite</a>(...);</code></pre>
+runner.<a href="/docs/test/runner/#runSuite">runSuite</a>(...);</code></pre>
<h3 id="quiet-reporter-sample">Sample output</h3>
<p><img src="/images/buster-test/quiet-reporter.png" width="661" height="34"></p>
</div>
@@ -157,7 +157,7 @@ <h3 id="xml-reporter-create" data-title="+create(options)+">
Create an instance.
</p>
<h3 id="xml-reporter-listen" data-title="+listen(testRunner)+">
- <code>listen(<a href="/docs/test/test-runner/">testRunner</a>)</code>
+ <code>listen(<a href="/docs/test/runner/">testRunner</a>)</code>
</h3>
<p>
Bind the reporter to a test runner.
@@ -166,10 +166,10 @@ <h3 id="xml-reporter-listen" data-title="+listen(testRunner)+">
var xmlReporter = require("buster-test").reporters.xml;
var reporter = xmlReporter.create({ color: false });
-var runner = testRunner.<a href="/docs/test/test-runner/#create">create</a>();
+var runner = testRunner.<a href="/docs/test/runner/#create">create</a>();
reporter.listen(runner);
-runner.<a href="/docs/test/test-runner/#runSuite">runSuite</a>(...);</code></pre>
+runner.<a href="/docs/test/runner/#runSuite">runSuite</a>(...);</code></pre>
<h3 id="xml-reporter-sample">Sample output</h3>
<p><img src="/images/buster-test/xml-reporter.png" width="780" height="837"></p>
</div>
@@ -193,7 +193,7 @@ <h3 id="html-reporter-create" data-title="+create(options)+">
Create an instance.
</p>
<h3 id="html-reporter-listen" data-title="+listen(testRunner)+">
- <code>listen(<a href="/docs/test/test-runner/">testRunner</a>)</code>
+ <code>listen(<a href="/docs/test/runner/">testRunner</a>)</code>
</h3>
<p>
Bind the reporter to a test runner.
@@ -202,18 +202,18 @@ <h3 id="html-reporter-listen" data-title="+listen(testRunner)+">
root: document.body // Full webpage mode
});
-var runner = buster.testRunner.<a href="/docs/test/test-runner/#create">create</a>();
+var runner = buster.testRunner.<a href="/docs/test/runner/#create">create</a>();
reporter.listen(runner);
-runner.<a href="/docs/test/test-runner/#runSuite">runSuite</a>(...);</code></pre>
+runner.<a href="/docs/test/runner/#runSuite">runSuite</a>(...);</code></pre>
<h3 id="html-reporter-sample">Sample output</h3>
<p><img src="/images/buster-test/html-reporter.png" width="604" height="810"></p>
</div>
<div class="section">
<h2 id="json-proxy"><code>jsonProxy</code></h2>
<p>
Not intended for human consumption. The jsonProxy reporter proxies all
- events from the <a href="/docs/test/test-runner/">test runner</a>, but strips any
+ events from the <a href="/docs/test/runner/">test runner</a>, but strips any
non-JSON safe value (such as functions). Buster uses this when emitting test
results from a browser to the server.
</p>
@@ -238,7 +238,7 @@ <h3 id="json-proxy-create" data-title="+create(emitter)+">
emit events directly over the wire.
</p>
<h3 id="json-proxy-listen" data-title="+listen(testRunner)+">
- <code>listen(<a href="/docs/test/test-runner/">testRunner</a>)</code>
+ <code>listen(<a href="/docs/test/runner/">testRunner</a>)</code>
</h3>
<p>
Bind the reporter to a test runner.
@@ -247,7 +247,7 @@ <h3 id="json-proxy-listen" data-title="+listen(testRunner)+">
<div class="section">
<h2 id="implement">Implementing a reporter</h2>
<p>
- Buster reporters consume events from a <a href="/docs/test/test-runner/"><code>buster.testRunner</code></a> instance and should conform to the
+ Buster reporters consume events from a <a href="/docs/test/runner/"><code>buster.testRunner</code></a> instance and should conform to the
simple API described below. For the reporter to be usable with Buster's
auto-wiring mechanism, you also need to make the reporter available as a
Node module. The auto-wiring mechanism is what is in use when you have not
@@ -272,7 +272,7 @@ <h2 id="implement">Implementing a reporter</h2>
<p>
This method allows you to listen to events of interest on the test
runner. The built-in reporters typically use <a href="/buster-event-emitter/#bind"><code>bind</code></a>, but you are completely free to implement this the
- way you feel best. See <a href="/docs/test/test-runner/#events">test runner events</a>
+ way you feel best. See <a href="/docs/test/runner/#events">test runner events</a>
for available events.
</p>
<h4>Include your reporter on the load path</h4>
View
4 site/docs/test/spec.html
@@ -15,8 +15,8 @@
<a href="/docs/test/test-case/"><code>buster.testCase</code></a> but with a syntax
closer to BDD-style frameworks such as <a href="http://rspec.info/">RSpec</a>,
<a href="http://pivotal.github.com/jasmine/">Jasmine</a> and others.
- <a href="#describe"><code>describe</code></a> produces <a href="/docs/test/test-context/"><code>buster.testContext</code></a> objects that can be run using
- <a href="/docs/test/test-runner/"><code>buster.testRunner</code></a>.
+ <a href="#describe"><code>describe</code></a> produces <a href="/docs/test/context/"><code>buster.testContext</code></a> objects that can be run using
+ <a href="/docs/test/runner/"><code>buster.testRunner</code></a>.
</p>
<h3>Unboxing the namespace</h3>
<p>
View
4 site/docs/test/stack-filter.html
@@ -38,8 +38,8 @@ <h3 id="stackFilter" data-title="+stackFilter(stack[, cwd])+">
'at fail (/home/christian/buster/node_modules/buster-assert/lib/buster-assert.js:61:16)' +
'at Function.equals (/home/christian/buster/node_modules/buster-assert/lib/buster-assert.js:237:13)' +
'at Object.&lt;anonymous&gt; (/home/christian/buster/doc/samples/test-case.js:101:23)' +
- 'at asyncFunction (/home/christian/buster/node_modules/buster-test/lib/buster-test/test-runner.js:79:21)' +
- 'at Object.runTestFunction (/home/christian/buster/node_modules/buster-test/lib/buster-test/test-runner.js:312:26)' +
+ 'at asyncFunction (/home/christian/buster/node_modules/buster-test/lib/buster-test/runner.js:79:21)' +
+ 'at Object.runTestFunction (/home/christian/buster/node_modules/buster-test/lib/buster-test/runner.js:312:26)' +
'at /home/christian/buster/node_modules/buster-core/lib/buster-core.js:45:31' +
'at runOne (/home/christian/buster/node_modules/buster-promise/lib/buster-promise.js:89:35)' +
'at Array.0 (/home/christian/buster/node_modules/buster-promise/lib/buster-promise.js:75:47)' +
View
4 site/docs/test/test-case.html
@@ -14,13 +14,13 @@
with some BDD idioms. <code>buster.testCase</code> supports setup and
teardown, asynchronous tests, nested test cases, deferred tests, and more.
<code>buster.testCase</code> produces <a href="/docs/test/test-context/"><code>buster.testContext</code></a> objects that can be run using
- <a href="/docs/test/test-runner/"><code>buster.testRunner</code></a>.
+ <a href="/docs/test/runner/"><code>buster.testRunner</code></a>.
</p>
<div>
<h2 id="testCase"><code>testCase(name, tests)</code></h2>
<p>
Returns a <a href="/docs/test/test-context/#testContext"><code>testContext</code></a>
- that can be run with <a href="/docs/test/test-runner/"><code>buster.testRunner</code></a>.
+ that can be run with <a href="/docs/test/runner/"><code>buster.testRunner</code></a>.
<code>name</code> is an arbitrary string. The <code>tests</code> object can
contain test functions, nested test cases, setup and teardown.
</p>

0 comments on commit d151865

Please sign in to comment.
Something went wrong with that request. Please try again.