[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ruby-talk
Subject:    Re: Whitestone 1.0.2
From:       Gavin Sinclair <gsinclair () gmail ! com>
Date:       2012-01-28 0:55:02
Message-ID: CAL2eo0f-_r-c5kmZ8eeisA1_e2HQrYxrcOp31jPRwFGRtDPokA () mail ! gmail ! com
[Download RAW message or body]

On Sat, Jan 28, 2012 at 3:38 AM, Jon Forums <jon.forums@gmail.com> wrote:
>> Key features of Whitestone include terse testing code, colorful and
>> helpful output, custom assertions, a powerful and intuitive test
>> runner, simple debugger integration. The homepage explains and
>> demonstrates it well.
>
> I just skimmed the homepage; what do you think are the _primary_
> pros/cons wrt minitest?

I wrote the key features with test/unit in mind because that's what I
was used to for years. Minitest may have implemented some of those; I
don't know. The only con I can think of is "not being a standard" but
that doesn't bother me.

If I have to pick _primary_ features then it's the first two:
 * terse testing code (I hate typing in lots of code to test things,
and want the focus to be on the code being tested)
 * colorful and helpful output (it gives a lot of information on
failures and errors and is easy to read)

If those features are matched by other testing libraries, I'm not
aware of it. But there are many of them, so ...

> How well does it work on Windows, specifically the `col` gem?
>
> =A0http://gsinclair.github.com/col.html#windows_users

Good question. I develop on Mac and when I use Ruby on Windows, it's
under Cygwin, which masks the Windows-compatibility problem.  I'll
look more into it.

> Note the `win32console` deprecation notice at
> https://github.com/luislavena/win32console and advocacy for
> https://github.com/adoxa/ansicon

Thanks for the pointer. I'll see if I can integrate it ASAP.

> Interesting output report style, any way to make it minimalist via a cmd
> line option or config?

No. Wouldn't be hard to implement, but it's not something I've
desired. I know minimalist output (or better yet, some standardised
yaml output or similar) is good for tapping into other products, like
continuous integration servers etc.  But that hasn't been relevant to
me so far.

Like many projects, it's designed to suit me perfectly :)

[prev in list] [next in list] [prev in thread] [next in thread]