Greenbar 1.0


#1

Announcing Greenbar.

Greenbar is an open source project intended to aid in the writing of
Test::Unit tests. It consists of a framework to aid in providing
reusable
chunks of setup and teardown code, and a handful of useful concrete
examples.

If you write automated tests for your code using Test::Unit, I’m sure
you’ll
find some value in Greenbar.

Greenbar is available as a ruby gem. The project home page is
http://greenbar.rubyforge.org. Full documentation is available on the
site.

David C.


#2

David C. wrote:

Announcing Greenbar.

From the title, I thought you were going to polish the
GUI testrunners…

Greenbar is an open source project intended to aid in the writing of
Test::Unit tests. It consists of a framework to aid in providing reusable
chunks of setup and teardown code, and a handful of useful concrete examples.

Color me stupid, but I couldn’t (quickly) uncover the
concrete examples in the documentation section of the
website.

Later,


#3

On 5/4/06, Bil K. removed_email_address@domain.invalid wrote:

Greenbar is an open source project intended to aid in the writing of
Test::Unit tests. It consists of a framework to aid in providing reusable
chunks of setup and teardown code, and a handful of useful concrete examples.

Color me stupid, but I couldn’t (quickly) uncover the
concrete examples in the documentation section of the
website.

Most of the class documentation pages include examples for that class.
For example,
http://greenbar.rubyforge.org/documentation/classes/Greenbar/ClassMethodSetup.html

Jacob F.


#4

On May 4, 2006, at 5:33 AM, David C. wrote:

find some value in Greenbar.

Greenbar is available as a ruby gem. The project home page is
http://greenbar.rubyforge.org. Full documentation is available on
the site.

require_gem is going away RSN, you shouldn’t be using it at all.
Instead just use require like normal.


Eric H. - removed_email_address@domain.invalid - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant

http://trackmap.robotcoop.com


#5

On May 4, 2006, at 10:54 AM, Mark V. wrote:

On 5/4/06, Eric H. removed_email_address@domain.invalid wrote:

require_gem is going away RSN, you shouldn’t be using it at all.
Instead just use require like normal.

I thought just the autorequire attribute in gemspecs was going away.
That currently allows you to use require_gem instead of require. Won’t
we still have to use require_gem, in addition to require, in order to
use a particular version of a gem instead of the latest version that
has been installed?

I believe the plan is to add a new method to handle activating a
particular version (and nothing more) and remove require_gem after a
deprecation period.

See:

http://rubyforge.org/pipermail/rubygems-developers/2006-April/
001927.html


Eric H. - removed_email_address@domain.invalid - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant

http://trackmap.robotcoop.com


#6

On 5/4/06, Eric H. removed_email_address@domain.invalid wrote:

require_gem is going away RSN, you shouldn’t be using it at all.
Instead just use require like normal.

I thought just the autorequire attribute in gemspecs was going away.
That currently allows you to use require_gem instead of require. Won’t
we still have to use require_gem, in addition to require, in order to
use a particular version of a gem instead of the latest version that
has been installed?