Issues

When the IoC testing framework times out waiting for an event it should unblock jqUnit so that the error is reported.

IoC Testing Framework always begins to construct first test environment grade immediately

It's inconvenient to not be able to use IoC expressions in a "modules" block of a testCaseHolder

The IoC testing framework should log a warning or failure if a test specification is malformed

IoC testing framework fails with unhelpful error message if "sequenceElements" property is not set in fluid.test.sequence

Rename member "elements" introduced in IoC Testing framework to "sequenceElements"

Modernise support in IoC Testing framework for "change" type fixtures

Eliminate fragile sequence array-building code in IoC Testing Framework in favour of "grade constraint budding system"

Error received when an ajax call back sets a model value on a component that has been destroyed

The test written in IoC testing framework runs fine on its own but throws error in all-tests.html

Allow IoC testing framework's testEnvironment to act as its own testCaseHolder

Listeners bound using the IoCSS syntax using the IoC testing framework are never unbound

IoC testing framework "event" fixture doesn't accept single-element "args" value

Timing of onTestCaseStart event is incorrect

onTestCaseStart event can fire multiple times in IoC Testing fixture

IoC testing framework mishandles any case of "two listeners in a row"

Implement "test case grade" to assist IoC-directed testing and event sequence testing