Improve output

[tindzk]

I just migrated one of my projects to otest and overall I'm quite happy with it. It even runs the test cases considerably faster than Jasmine. However, I find the output rather hard to read. For a quick comparison, see the following links:

Before: https://travis-ci.org/widok/widok/builds/40244261
After: https://travis-ci.org/widok/widok/builds/40319386

My suggestions are:

• Remove the trailing dollar sign after the class name
• Indent the tests
• Use Unicode indicators ✓and ✗
• Only use colours for the indicators, rather than for the whole line
• Move the timers to the end for each test case for better alignment
• Add an option to entirely disable the timers
• Don't print stack traces for assertions (Expected $value to be $expected. suffices)

[benjaminjackman]

Hey thanks for the feedback! Those are really good suggestions! I'll add
them to the todo list.

On Fri, Nov 7, 2014 at 1:07 PM, Tim Nieradzik notifications@github.com
wrote:

I just migrated one of my projects to otest and overall I'm quite happy
with it. It even runs the test cases considerably faster than Jasmine.
However, I find the output rather hard to read. For a quick comparison, see
the following links:

Before: https://travis-ci.org/widok/widok/builds/40244261
After: https://travis-ci.org/widok/widok/builds/40319386

My suggestions are:

• Remove the trailing dollar sign after the class name
• Indent the tests
• Use Unicode indicators ✓and ✗
• Only use colours for the indicators, rather than for the whole line
• Move the timers to the end for each test case for better alignment
• Add an option to entirely disable the timers
• Don't print stack traces for assertions (Expected $value to be
  $expected. suffices)

—
Reply to this email directly or view it on GitHub
#1.