Task #68

Evaluate testing frameworks

Added by Colin Snover about 5 years ago. Updated almost 5 years ago.

Status:New Start date:08/15/2012
Priority:Normal Due date:08/29/2012
Assignee:- % Done:

0%

Category:-
Target version:-

Description

Before work on Dojo 2 begins we need to decide on a testing framework. Please provide feedback and an evaluation will be made as to the best choice.

History

Updated by Colin Snover almost 5 years ago

How would we like testing to work? User story:

I would like to be able to write test modules using AMD and has.js APIs.
I would like to be able to write assertions using an assert-style API.
I would like to be able to run individual tests from within my browser without needing to load Java or Node.js.
I would like to be able to run individual tests from the command line using Node.js.
I would like to be able to receive a code coverage report after my tests have finished running alongside the test results.
I would like to be able to specify performance thresholds for tests and receive information on whether the tests are running slowly.
I would like to be able to specify how many assertions are expected per test.
I would like to be able to perform automated functional testing using the WebDriver API.
I would like to be able to have a continuous integration server automatically run the entire test suite whenever a new commit is pushed.
I would like to be able to have a continuous integration server automatically run the entire test suite whenever a new pull request is added to the queue.

Also available in: Atom PDF