# Greenbar 1.0 **URL:** \ **Category:** Ruby\ **Created:** [May 4, 2006, 2:34pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476 "2006-05-04T14:34:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![crucoba](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@crucoba](https://www.ruby-forum.com/u/crucoba)\ **Post date:** [May 4, 2006, 2:34pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476/1 "2006-05-04T14:34:50Z")
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](http://greenbar.rubyforge.org). Full documentation is available on the site. David C. ---
**Author:** ![crucoba](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@crucoba](https://www.ruby-forum.com/u/crucoba)\ **Post date:** [May 4, 2006, 3:17pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476/2 "2006-05-04T15:17:53Z")
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, ---
**Author:** ![crucoba](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@crucoba](https://www.ruby-forum.com/u/crucoba)\ **Post date:** [May 4, 2006, 5:52pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476/3 "2006-05-04T17:52:57Z")
On 5/4/06, Bil K. [removed\_email\_address@domain.invalid](mailto: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](http://greenbar.rubyforge.org/documentation/classes/Greenbar/ClassMethodSetup.html) Jacob F. ---
**Author:** ![crucoba](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@crucoba](https://www.ruby-forum.com/u/crucoba)\ **Post date:** [May 4, 2006, 7:49pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476/4 "2006-05-04T19:49:03Z")
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](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](http://blog.segment7.net) This implementation is HODEL-HASH-9600 compliant [http://trackmap.robotcoop.com](http://trackmap.robotcoop.com) ---
**Author:** ![crucoba](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@crucoba](https://www.ruby-forum.com/u/crucoba)\ **Post date:** [May 4, 2006, 8:01pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476/5 "2006-05-04T20:01:20Z")
On May 4, 2006, at 10:54 AM, Mark V. wrote: > On 5/4/06, Eric H. [removed\_email\_address@domain.invalid](mailto: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/](http://rubyforge.org/pipermail/rubygems-developers/2006-April/) 001927.html – Eric H. - removed\_email\_address@domain.invalid - [http://blog.segment7.net](http://blog.segment7.net) This implementation is HODEL-HASH-9600 compliant [http://trackmap.robotcoop.com](http://trackmap.robotcoop.com) ---
**Author:** ![crucoba](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@crucoba](https://www.ruby-forum.com/u/crucoba)\ **Post date:** [May 4, 2006, 7:55pm UTC](https://www.ruby-forum.com/t/greenbar-1-0/94476/6 "2006-05-04T19:55:09Z")
On 5/4/06, Eric H. [removed\_email\_address@domain.invalid](mailto: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?