Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Removed unit test refactoring mention from README.todo

  • Loading branch information...
commit 54fec8e5c683720e63114d5997478812913f1ba2 1 parent d4c83a1
@mikegerwitz authored
Showing with 0 additions and 23 deletions.
  1. +0 −23 README.todo
View
23 README.todo
@@ -13,29 +13,6 @@ resulted in a tightly coupled system that was difficult to maintain, add to and
test. Refactoring into prototypes is ongoing.
-UNIT TESTS
-----------
-The unit tests are currently split between a few different formats, depending on
-filename and test construction.
-
-- Tests created during the beginning of the project have a test-* prefix. These
- are more likely to represent integration or system tests rather than unit
- tests. They should be converted to files with a *Test.js suffix and be
- refactored to test only the unit.
-- Newer tests use require( 'common' ).testCase() in order to run the tests. The
- older format separates tests with self-executing functions. The former should
- be used.
-
-When running the tests, you will notice that the older tests output nothing
-whereas the newer tests output the status of each test in addition to a summary
-at the end of the test case. Ultimately, a test runner will defer final
-statistics until the end of all running tests. The Makefile will need to be
-modified. This sacrifices the ability to use -jN with the tests, but will
-ultimately speed up the tests by eliminating the need to run a separate process
-for each test case (the performance benefit can be seen by running the tests in
-the browser).
-
-
PERFORMANCE TESTS
-----------------
Performance tests need to be written for every aspect of the system. They will
Please sign in to comment.
Something went wrong with that request. Please try again.