Home ›

How to Use ZenTest with Ruby

Sep 14, 2004  By Pat Eyler
 in
An introduction to using refactoring, unit testing and ZenTest on existing code.
Resources

If you're interested in learning more about refactoring, grab a copy of Refactoring: Improving the Design of Existing Code and take a look at www.refactoring.com. For more information about unit testing, please see c2.com/cgi/wiki?UnitTest www.junit.org/index.htm and www.extremeprogramming.org/rules/unittests.html.

The latest information about Test::Unit and ZenTest can be found on theirs home pages, testunit.talbott.ws and www.zenspider.com/ZSS/Products/ZenTest.

______________________

-- -pate http://on-ruby.blogspot.com

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Concatenate strings with << instead

Roman2K's picture
Submitted by Roman2K (not verified) on Fri, 01/19/2007 - 08:29.

Avoid concatenating strings using += because it duplicates the receiver string that will remain unused in memory until the GC starts. You should rather use << that modifies the receiver by appending the given string to it. It's also quite faster.

... continuation of the above comment discussing the << operator

Roman2K's picture
Submitted by Roman2K (not verified) on Fri, 01/19/2007 - 08:35.

(sorry for the truncated comment above) ... You should rather use the double "lower than" operator (cannot be written here or the comment gets cut) that modifies the receiver appending the given string to it and returns the string to allow chained calls. It's also quite faster.

Note that Ryan has moved Zentest to RubyForge...

Tom Copeland's picture
Submitted by Tom Copeland (not verified) on Mon, 12/06/2004 - 14:23.

....right here.

Yours,

Tom

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Wed, 09/15/2004 - 02:00.

I don't think assert(1) is a good thing. That test should fail, imo. Maybe raising something like NotImplementedError would be better.
A pleasant article, anyway, now I'm wondering how cool an integration of ZenTest with FreeRIDE (and the included Refactoring-Browser plugin) could be..

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Thu, 09/16/2004 - 02:00.

Great idea for another article or two!

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Wed, 09/15/2004 - 02:00.

ooh -- ZenTest, rrb, and FreeRIDE together? that sounds really good! Rich, Ryan? are you guys listening?

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Fri, 09/17/2004 - 02:00.

you can try it yourself :)
I wrote a simple test generation plugin long time ago (see DumbTestBuilder on the FR wiki) in an hour, and I had never used the FreeRIDE/FreeBASE api before..

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Wed, 09/15/2004 - 02:00.

the assert(1) test set my alarm bells ringing, but I see your point...

Test::Unit is Another Good Reason To Use Ruby, but I always find myself copying an existing testsuite and editing because I cant' remember syntax worth a damn, so anything that bootstraps a test*rb creation is worth its weight in gold..

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Tue, 09/14/2004 - 02:00.

Excellent. I always wondered what was the easiest way of adding unit tests and what you show here is really simple and straightforward. I love it.

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Tue, 09/14/2004 - 02:00.

Hey, that's excellent! Thanks for the article.

--Gavin Sinclair

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Tue, 09/14/2004 - 02:00.

Never used ZenTest before, but it seems like a good way to get started with adding unit testing to those old project I started before I learned how to write decently tested code.
I always like helpers that save me a step or two.

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Tue, 09/14/2004 - 02:00.

I had never looked into ZenTest, but now that I realize it creates Test::Unit tests for you, it does sound like a great way to deal with legacy (i.e., "not written test-first", in TDD parlance) code.

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Mon, 09/27/2004 - 02:00.

ZenTest is bidirectional, so it is also a great way to do test-first. Write the tests, run them... throw exceptions galore because the classes referenced do not exist. ZenTest will fill in those blanks for you as well.

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Tue, 09/14/2004 - 02:00.

Very cool article. I often scan over the code with my eyes and see what I am missing and try to do the refactoring manually. I had never heard of Zentest before this article. I will have to check it out....it looks like it'll make my life easier and less error prone. ;)

Re: How to Use ZenTest with Ruby

Anonymous's picture
Submitted by Anonymous on Tue, 09/14/2004 - 02:00.

Wow! ZenTest looks like a really cool way to generate the unit testing scaffolding code. Looks like it takes the tedium out of unit testing.

Very informative.

It would be great to see more Ruby articles like this as well.

thanks for great article,

polypus's picture
Submitted by polypus (not verified) on Wed, 05/10/2006 - 10:01.

thanks for great article, will try zentest

just to point out typo, in last assertion here, no closing paren

def test_name=
aCustomer = Customer.new("Fred Jones")
assert_equal("Fred Jones",aCustomer.name)
aCustomer.name = "Freddy Jones"
assert_equal("Freddy Jones",aCustomer.name
end

can testers use this for functional testing

Anonymous's picture
Submitted by Anonymous (not verified) on Thu, 08/09/2007 - 05:15.

can testers use this for functional testing?.
(or)
Developers can use it...

pls let me know.if tester can use this, what are the things he wants to know

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions