Permalink
Browse files

Remove suiteSetup/suiteTeardown from test toSting in wrap

  • Loading branch information...
1 parent f08f89c commit e4e37799684e3b98af21c63fd216ed6938deff5d Benjamin Thomas committed Oct 28, 2010
Showing with 9 additions and 9 deletions.
  1. +8 −6 lib/wrap.js
  2. +1 −3 todo.txt
View
@@ -96,13 +96,15 @@ exports.wrap = function(obj) {
});
}
+ var prevToString = func + '';
n.toString = function() {
- var str = '';
- for (var i = 0; i < n.length; i++) {
- if (n[i] != empty) {
- str += n[i]+'\n';
- }
- }
+ var str =
+ '' +
+ (obj.setup ? obj.setup + '\n' : '') +
+ prevToString + '\n' +
+ (obj.teardown ? obj.teardown + '' : '')
+ ;
+
return str;
}
View
@@ -12,10 +12,8 @@ async_testing.run: make it so run can take any combination of the following...
async_testing.run(process.ARGV.slice(1), {parallel: true}) // parallel no matter what
and so on
-Wrap: don't output the suiteSetup/suiteTeardown functions in the toString for a test
-
Console Runner: readd number of completed tests back to summary in console runner
-Console Runner: are we being too redundant when
+Console Runner: are we being too redundant when we have errors?
Web Runner: checkbox for web runner to automatically run suites on window or tab focus
Web Runner: keep track of which suites have been opened and are parallel across refreshes

0 comments on commit e4e3779

Please sign in to comment.