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.

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?

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.3.3 / 2010-06-17

• 2 minor enhancements:

  • Added options and removed pattern from Autotest::RCov
  • update_rubygems now deletes cached rubygems installs

• 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.3.2 / 2010-06-02

• 1 minor enhancement:

  • Removed support for rbx builds.

• 2 bug fixes:

  • Removed 'preview' from version filter so I can test with 1.9.2
  • Put PATH tweaks at front of PATH

• 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.3.1 / 2010-03-30

• 1 bug fix:

  • Fixed autotest output on 1.8. That's what I get for not having tests for dots.

• 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.3.0 / 2010-03-27

• 1 minor enhancement:

  • Added gemcutter rubyforge and hoe to the_usual setup

• 4 bug fixes:

  • 1.9 compat: don't use putc anymore. (fistfvck (hah!))
  • Added note that included articles are out of date
  • Fixed rcov plugin so multiple all_good hooks can coexist
  • Fixed typo in doco

• 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.2.1 / 2009-12-09

• 1 minor enhancement:

  • Added GEMHOME/GEMPATH setting to multiruby.

• 1 bug fix:

  • Fixed multiruby refactoring bug from previous release.

• 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.2.0 / 2009-12-08

• 3 minor enhancements:

  • Added 'multiruby -1 $version' for easier execution (idea from flori)
  • Set up and tear down PATH in multiruby (luis)
  • died hook now gets passed the exception (amikula)

• 3 bug fixes:

  • Deal with windoze getc returning nil (undees)
  • Fix unit_diff for multiline miniunit results.
  • Fix warning for 1.8.8+

• 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.1.4 / 2009-08-07

• 2 minor enhancements:

  • Added ability to prepend file mappings in autotest. (irohiroki)
  • Switched autodiscover to use Gem.find_files.

• 2 bug fixes:

  • Updated doco for API changes. (David Ruan)
  • Updated git URL for Rubinius. jbarnette

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

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