# ZenTest 3.1.0 Released **URL:** \ **Category:** Ruby\ **Created:** [March 30, 2006, 12:55am UTC](https://www.ruby-forum.com/t/zentest-3-1-0-released/56299 "2006-03-30T00:55:02Z")\ **Posts on this page:** 3\ **Page:** 1
**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:** [March 30, 2006, 12:55am UTC](https://www.ruby-forum.com/t/zentest-3-1-0-released/56299/1 "2006-03-30T00:55:02Z")
ZenTest version 3.1.0 has been released! [http://www.zenspider.com/ZSS/Products/ZenTest/](http://www.zenspider.com/ZSS/Products/ZenTest/) == DESCRIPTION ZenTest provides 4 different tools: zentest, unit\_diff, autotest, and multiruby. 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! There are two strategies intended for ZenTest: test conformance auditing and rapid XP. For auditing, ZenTest provides an excellent means of finding methods that have slipped through the testing process. I’ve run it against my own software and found I missed a lot in a well tested package. Writing those tests found 4 bugs I had no idea existed. ZenTest can also be used to evaluate generated code and execute your tests, allowing for very rapid development of both tests and implementation. == FEATURES/PROBLEMS - Scans your ruby code and tests and generates missing methods for you. - Includes a very helpful filter for Test::Unit output called unit\_diff. - Continually and intelligently test only those files you change with autotest. - Test against multiple versions with multiruby. - Not the best doco in the world (my fault) - Includes a LinuxJournal article on testing with ZenTest written by Pat Eyler. - See also: [http://blog.zenspider.com/archives/zentest/](http://blog.zenspider.com/archives/zentest/) Changes: - 2 major enhancements - 10 minor enhancements - 4 bug fixes – \_why: zenspider’s most intense moments of solice are immediately following the slaughter […] \_why: that topknot’s the only thing keeping a lid on the righteous anger bricolage: yeah, that and his flagrant obsession with dvorak ---
**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:** [March 30, 2006, 7:22am UTC](https://www.ruby-forum.com/t/zentest-3-1-0-released/56299/2 "2006-03-30T07:22:32Z")
Sounds excellent! A few things which I would really like: 1. When a test fails, hyperlink the output to the line of code in the source (somehow - not sure how this could be implemented), or at least print out the relevant line of the source. 2. Print out the last few lines of the log as well (maybe proxy logger - I actually wrote some code to do this). 1. Do the above with color coding, where avaible. 2. Add a system tray icon with a green, red, or gray (in process of running) light. (Although I know of no cross OS way to do this.) ---
**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:** [March 30, 2006, 11:37pm UTC](https://www.ruby-forum.com/t/zentest-3-1-0-released/56299/3 "2006-03-30T23:37:38Z")
On Mar 29, 2006, at 9:18 PM, removed\_email\_address@domain.invalid wrote: > A few things which I would really like: > > 1. When a test fails, hyperlink the output to the line of code in the > source (somehow - not sure how this could be implemented), or at least > print out the relevant line of the source. I never touch the mouse while writing code and I’m typically on or near the failing lines. autotest really helps out with that because it lets you focus your efforts. Typically make parsing is a function of your editor, so you should be able to adapt it to understand Test::Unit output. > 1. Print out the last few lines of the log as well (maybe proxy logger > > - I actually wrote some code to do this). If you have to look at some log to figure out how to fix your tests you don’t have enough tests. Good test coverage will give you granular failures. To my knowledge, most code that has tests doesn’t log anything. > 1. Do the above with color coding, where avaible. Yuck. > 1. Add a system tray icon with a green, red, or gray (in process of > running) light. (Although I know of no cross OS way to do this.) We don’t do windows, but we accept patches. – 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)