RushCheck http://rushcheck.rubyforge.org/ a lightweight random testing tool for Ruby en-US hourly 1 1970-01-01T00:00:00+09:00 delaying http://rushcheck.rubyforge.org//posts/20061204-delaying.html Why does the development of Rushcheck seem to be delayed? There are several reasons that I may have to say. The main reason is that I'm now concentrate upon writing a paper whose deadline is Jan 8, 2007, which is not related to RushCheck, but my favorite mathematics. On the other hand, another reasons are related to RushCheck. I've two talks about the library at local seminars in Japan. One has already given and you can see "the slide of talk.":http://madscientist.jp/~ikegami/diar...(snip) 2006-12-05T07:53:16+09:00 RushCheck0_7 http://rushcheck.rubyforge.org//posts/20061028-RushCheck0_7.html Now I'm writing testcases for RushCheck by "RSpec":http://rspec.rubyforge.org. Because some tests or specifications requires many instances, I think they should be generated randomly as random testing. I'm very happy because now RushCheck can be used to test RushCheck itself! This means the status of RushCheck becomes more stable. Though I've not finished writing test cases, I decide to ship the next version 0.7 because "reck wreck", who tried RushCheck, reported a bug at "the discus...(snip) 2006-10-28T09:55:57+09:00 CombineAnotherTestingFramework http://rushcheck.rubyforge.org//posts/20061008-CombineAnotherTestingFramework.html In this article, I will introduce how to combine Ruby's unit testing 'test/unit' and RushCheck. I have also tried "RSpec":http://rspec.rubyforge.org which supports BDD (Behaviour Driven Development) style checking specifications. To watch the testing code, we need a target of tests. I quote the following simple example from "the tutorial of RSpec":http://rspec.rubyforge.org/tutorials/index.html. <pre> # stack.rb class Stack def initialize @stack = [] end def empty? @st...(snip) 2006-10-13T03:57:20+09:00 ShippingVer4 http://rushcheck.rubyforge.org//posts/20061006-ShippingVer4.html I am happy to announce the next version of RushCheck. I have done many bug fixes and change some main interfaces. Especially, the notation of pre-condition with guards is changed. From this version, the number of a block of assertion must be equal to the number of arguments of Assertion.new. before: <pre> Assertion.new(Integer, String) do |x, y, g| g.guard { # a pre-condition here } ... end </pre> after: <pre> RushCheck::Assertion.new(Integer, String) do |x, y| RushCheck::guard...(snip) 2006-10-07T04:38:08+09:00 MovedToDarcs http://rushcheck.rubyforge.org//posts/20060818-MovedToDarcs.html <p> Because I prefer "darcs":http://www.abridgegame.org/darcs/ than CVS, RushCheck has moved to a darcs repository. No changes should be committed to the CVS repository at RubyForge from now on. You can get the latest development version of RushCheck by </p> <pre> % darcs get --partial http://rushcheck.rubyforge.org/repos/rushcheck </pre> <p> Then you can get all new patches from the main repository whenever after cd the repository by </p> <pre> % darcs pull -a </pre> <p> Unfortunately...(snip) 2006-08-18T06:19:47+09:00 RushCheckNew http://rushcheck.rubyforge.org//posts/20060809-RushCheckNew.html 2004-05-11, Prof. John Hughes visited our laboratory and gave his talk "Random Testing with QuickCheck" at the 1st workshop on "Types for Verification". Because his talk was interesting for us, Sakai-san and I discussed to him in detail at the next day. At that time, I started to implement "QuickCheck":http://www.cs.chalmers.se/~rjmh/QuickCheck/ in Ruby, however, hacking was interrupted so often. Then suddenly I lost any files by disk crash and I have no backup unfortunately. 2 y...(snip) 2006-08-11T19:07:02+09:00