If at any point you think of an experiment you'd like to try out, all of the code examples below are editable.

You can learn more about assert in another section of the documentation. Basically, assert is the main assertion engine that test uses to know whether or not a test has passed.

Tests are resolved using native Promise rules. If you're familiar with how async code works, you already know how test chaining works.

Failed tests don't call any of their children. You can use this to make your test suite "fail fast". For example, if a database connection fails, there's no point in running tests that rely on that connection, and there's no point in cluttering up your test output with those extra failures.

Eliminating superfluous tests will make it easier to see the root cause of that particular failure.

You can traverse your entire test tree at any point, even while a suite is running. This is rarely necessary, but can be occasionally used in powerful ways to build very creative extensions or test reporters.

Of course, Distilled is designed to be highly extensible.


Code samples in this section demonstrate bug fixes. They're not particularly relevant to the documentation, but they help make sure that Distilled never has any regressions.