Recently in ZenTest Category

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

unitdiff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong. Do note that minitest 2.2+ provides an enhanced assertequal obviating the need for unit_diff

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! Use multiruby_setup to manage your installed versions.

Changes:

4.6.2 / 2011-08-24

• 1 minor enhancement:

  • Added Autotest Tips section to Readme

• 1 bug fix:

  • Fixed mri 1.9.3 change to Find.find with autotest/restart and missing files.

• https://github.com/seattlerb/zentest

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

unitdiff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong. Do note that minitest 2.2+ provides an enhanced assertequal obviating the need for unit_diff

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! Use multiruby_setup to manage your installed versions.

Changes:

4.6.1 / 2011-08-11

• 3 bug fixes:

  • Fix for option flags and unhandled error warning in autotest. (dbackeus)
  • Fix option w/ args handling and restart by storing ARGV in options[:args]
  • Fixed autotest --rc option handling. (simplybusiness)

• https://github.com/seattlerb/zentest

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

unitdiff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong. Do note that minitest 2.2+ provides an enhanced assertequal obviating the need for unit_diff

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! Use multiruby_setup to manage your installed versions.

Changes:

4.6.0 / 2011-07-22

• 6 minor enhancements:

  • Added -p (plain diff) and made -u (unified diff) the default for unit_diff.
  • Added ./tmp to default exclusions.
  • Autotest defaults unitdiff to nil now, to allow minitest's enhanced assertequal to shine.
  • Autotest will raise if the :died handler doesn't handle the exception. (ralfebert)
  • Dropped 1.8.6 as a default tag/branch to build in multiruby.
  • autotest can now be automatically 'narrowed' on the command-line.
  • eg: autotest lib test/test_blah.rb

• 7 bug fixes:

  • Believe it or not... but some ppl use zentest. Fixed nested class vs module bug
  • Fix to turn on jruby's support for ObjectSpace. (stepheneb)
  • Fixed a rubygems deprecation in autotest
  • Fixed unit_diff scanning for minitest output.
  • Normalized shebangs to fix problems on windows (luis)
  • autotest/isolate.rb sets GEMHOME as well as GEMPATH.
  • Fixed 1.9.3 warnings.

• https://github.com/seattlerb/zentest

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

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! Use multiruby_setup to manage your installed versions.

Changes:

4.5.0 / 2011-02-18

• 6 minor enhancements:

  • Added autotest -w flag to turn on warnings. Turned off warnings by default.
  • Added autotest/preload.rb to deal with rails being egregiously slow.
  • Added child process handling/cleanup on signals.
  • Added postinitialize hook.
  • Improved restart mechanism to include all flags.
  • Refactored restart plugin to Autotest#restart.

• 5 bug fixes:

  • Added sigquit handler to restart app straight up.
  • Fixed autotest/isolate so it works
  • Fixed parse_options to take args array (default ARGV) and to be non-destructive.
  • Strip ascii color to avoid false positives. (graemeworthy)
  • Use RbConfig to remove warning

• http://www.zenspider.com/ZSS/Products/ZenTest/

• http://rubyforge.org/projects/zentest/
• ryand-ruby@zenspider.com

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

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! Use multiruby_setup to manage your installed versions.

Changes:

4.4.2 / 2010-12-10

• 2 bug fixes:

  • Added a temporary hack to deal with rspec(2?) discovery hacks.
  • Fixed windoze detection for unit_diff (thyresias)

• http://www.zenspider.com/ZSS/Products/ZenTest/

• http://rubyforge.org/projects/zentest/
• ryand-ruby@zenspider.com

This is a stub gem to fix the confusion caused by autotest being part of the ZenTest suite.

Changes:

4.4.6 / 2010-12-01

• This release deprecates/retires this gem and brings autotest back under ZenTest.

• http://www.zenspider.com/ZSS/Products/ZenTest/

• http://rubyforge.org/projects/zentest/
• ryand-ruby@zenspider.com

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

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! Use multiruby_setup to manage your installed versions.

Changes:

4.4.1 / 2010-12-01

• 12 minor enhancements:

  • Merged in most things from the autotest gem:
  • Added --no-full-after-failed. (grosser)
  • Added --rc path-to-dot-autotest. (grosser)
  • Added --style autotest-style. (grosser)
  • Added clarification comments. (grosser)
  • Added rake task descriptions. (grosser)
  • Switched to optparse. (grosser)
  • Switched windoze detection. (grosser, tenderlove)
  • Did not merge test parallelization. It should be a plugin. Awaiting patch.
  • Added autotest/bundler plugin.
  • Added autotest/isolate plugin.
  • Added capture of skips (for minitest) from result line.
  • Added focus_re to focus.rb.
  • Added latest_results hash.
  • Cleaned up unit_diff matcher by using any?
  • Enhanced the help/usage for autotest and zentest. (hugh sasse)
  • Refactored autotest runner discovery.
  • Refactored ruby_cmd to allow plugins to affect ruby execution.
  • Removed befuddling override of Dir.[] from 2007. shrug
  • Removed deny method in favor of aliasing refute.

• 2 bug fixes:

  • 1.9 shadowed variable fix
  • autotest/restart now passes ARGV back through to exec. yay!

• http://www.zenspider.com/ZSS/Products/ZenTest/

• http://rubyforge.org/projects/zentest/
• ryand-ruby@zenspider.com

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. Nobody uses this tool anymore but it is the package namesake, so it stays.

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! Use multiruby_setup to manage your installed versions.

Changes:

4.4.0 / 2010-09-01

• 1 major enhancement:

  • Removed git building. I'm dropping direct support for rubinius.

• 3 minor enhancements:

  • Added multiruby mri:list:x.y.z command so you can see what's available.
  • Enabled installing specific patch versions of ruby.
  • multiruby rubygems:update now forces a build to be less confusing.

• 1 bug fix:

  • Removed redundant testtonormal, now in zentest_mappings

• http://www.zenspider.com/ZSS/Products/ZenTest/

• http://rubyforge.org/projects/zentest/
• ryand-ruby@zenspider.com

rene_mendoza just posted a neat adaptation of autotest for RubyKoans. It uses autotest to run the koans and is complete with coloring. Check it out and enjoy accelerated ruby learning.

I've been working on this idea with autotest.

Here is the state machine that autotest currently uses:

Autotest starts by running all tests. When there is a failure, autotest reruns the failures until they're all passing. Once they're all passing, autotest reruns all tests to ensure you didn't break anything.

This last state transition from red to green is where I'd like to change things. Here is what I'm thinking:

I want to make a stack, a tree really, of failure paths. These paths will be defined by the autotest "flavor" that is running (vanilla, rails, rspec, etc.). Illustrated above is a fictional rails setup with failures. The top two boxes are the same scenario and run the same.

On the left is "feature development mode". (I'm not settled on these names.) In that mode, autotest would run all leaf nodes all the time. After getting testa to pass, the other test failures would rerun as well as moving up to running all of testx.rb to verify nothing else in test_x.rb is broken. This strategy is specialized to provide the absolute fastest feedback you can get with a minimal amount of extra tests run on any given pass.

On the right is "refactoring mode". In that mode, autotest would run all failures at the deepest stratum. After getting test_a to pass, autotest reruns the other failing test methods. Once they're all passing, it moves up one level and reruns the failing test files. This strategy is specialized to allow you to focus on fixing intentional breakage as you refactor or otherwise change a single point in your code.

The difference between the two is potentially subtle. I'm not entirely sure it is necessary at this point... but I need to run with both strategies in order to really tell.

What do you think? Is refactoring mode necessary? Is this entire thing overkill?