What makes up a test?

FuncUnit provides the basic structure needed to

write unit or functional tests.

Modules

Tests

Assertions

Tests

Tests are the individual building blocks of

your unit tests and are the "thing" you are testing.

test("No cookie, should land on login screen (ui only)", function() {
    expect(2);
    ok(S("input[name='user']"), "User field exists");
    ok(S("input[name='password']"), "Password field exists");
});

Modules

Modules are groups of tests with

setup and teardown methods that run for each test.

module("Contacts", {
  // runs before each test
  setup: function(){
    // setup code
  },
  // runs after each test
  teardown: function(){
    // cleanup code
  }
})

Assertions

Assertions are the essential element of any unit test.

The test author expresses the results expected (assertions) and FuncUnit compares the assertions to the actual values that an implementation produces.

test("counter", function() {
  ok(Conctacts.first().name, "there is a name property");
  equal(Contacts.counter(), 5, "there are 5 contacts");
});

Built-in Assertions

FuncUnit has several built-in assertions that you will use.

Here are a few of the more common ones you'll use but, there are others.

equal();
expect();
notEqual();
ok();
strictEqual()

Setting up your test

Sometimes you'll want to open a specific HTML page to test your code and other times you can use the default FuncUnit space to test your module. This is ESPECIALLY helpful when you need to test against a specific FIXTURE arrangement.

module("autosuggest",{
  setup: function() {
    S.open('autosuggest.html')
  }
});

"S" is a copy of the jQuery "$" method. It is used to find elements in the page you're testing. But, it works slightly differently than $.

The following uses S.open(URL) to open a file before every test.

The "S Method"

The S method accepts any valid jQuery selector string, just like $.

One difference from $ is that this query will happen in the context of the window of the page you're testing, not the FuncUnit page where it runs.

Depending on the context in which S is called, this selector may be used immediately and return a jQuery collection,

or

it may cache the selector, which will be used in the asynchronous queue later to find elements when previous queued methods have finished.

Why "S"?

S is a "copy" of $, created using jQuery.sub.

All the jQuery methods that FuncUnit doesn't

overload are callable on S collections.

The reason for this is to preserve jQuery in the test page, unmodified.

If you want to use jQuery, none of its

methods are modified.

jQuery can be used to do unit testing, or to directly access the test page and do custom things.

Modules

Modules are groups of tests with setup and teardown methods that run for each test.

All tests that occur after a call to module("Module Name") will be grouped into that module. The test names will all be preceded by the module name in the test results. You can then use that module name to select tests to run.

For example...