# ZenTest 3.9.1 Released

**URL:** <https://www.ruby-forum.com/t/zentest-3-9-1-released/127771>\
**Category:** Ruby\
**Created:** [February 1, 2008, 5:06am UTC](https://www.ruby-forum.com/t/zentest-3-9-1-released/127771 "2008-02-01T05:06:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [February 1, 2008, 5:06am UTC](https://www.ruby-forum.com/t/zentest-3-9-1-released/127771/1 "2008-02-01T05:06:10Z")

</div>

ZenTest version 3.9.1 has been released!

- [http://www.zenspider.com/ZSS/Products/ZenTest/](http://www.zenspider.com/ZSS/Products/ZenTest/)
- [http://rubyforge.org/projects/zentest/](http://rubyforge.org/projects/zentest/)
- [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

ZenTest provides 4 different tools and 1 library: zentest, unit\_diff,  
autotest, multiruby, and Test::Rails.

ZenTest scans your target and unit-test code and writes your missing  
code based on simple naming rules, enabling XP at a much quicker  
pace. ZenTest only works with Ruby and Test::Unit.

unit\_diff is a command-line filter to diff expected results from  
actual results and allow you to quickly see exactly what is wrong.

autotest is a continous testing facility meant to be used during  
development. As soon as you save a file, autotest will run the  
corresponding dependent tests.

multiruby runs anything you want on multiple versions of ruby. Great  
for compatibility checking!

Test::Rails helps you build industrial-strength Rails code.

Changes:

### 3.9.1 / 2008-01-31

- 1 bug fix:

- [http://www.zenspider.com/ZSS/Products/ZenTest/](http://www.zenspider.com/ZSS/Products/ZenTest/)

- [http://rubyforge.org/projects/zentest/](http://rubyforge.org/projects/zentest/)

- [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [February 1, 2008, 7:50am UTC](https://www.ruby-forum.com/t/zentest-3-9-1-released/127771/2 "2008-02-01T07:50:28Z")

</div>

Out of curiosity, what was the source of the leak?

---

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [February 1, 2008, 4:58pm UTC](https://www.ruby-forum.com/t/zentest-3-9-1-released/127771/3 "2008-02-01T16:58:32Z")

</div>

Many thanks for the quick update. I really enjoy the ZenTest suite.

James H.

---

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [February 1, 2008, 11:19pm UTC](https://www.ruby-forum.com/t/zentest-3-9-1-released/127771/4 "2008-02-01T23:19:45Z")

</div>

On Jan 31, 2008, at 22:49 , Rob S. wrote:

> Out of curiosity, what was the source of the leak?

stupidity.

---

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [February 1, 2008, 5:31pm UTC](https://www.ruby-forum.com/t/zentest-3-9-1-released/127771/5 "2008-02-01T17:31:58Z")

</div>

Ryan D. wrote:

> - 1 bug fix:
> 
> - [http://www.zenspider.com/ZSS/Products/ZenTest/](http://www.zenspider.com/ZSS/Products/ZenTest/)
> 
> - [http://rubyforge.org/projects/zentest/](http://rubyforge.org/projects/zentest/)
> 
> - [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

At least on Linux (and probably MacOS, but I don’t have one handy) one  
could, in fact, write a Spec/Assertion/whatever that tracked process  
size and its growth and delivered a red light if a threshold in size or  
growth rate was exceeded. I know there’s a way to do it on Windows, too,  
I just don’t remember what it is.

Something like

process.resident\_size should\_be \< 128 :megabytes
