From: "ara.t.howard" <ara.t.howard@...>
Date: 2008-12-18T13:40:50+09:00
Subject: Re: Writing a good spec.


On Dec 17, 2008, at 8:40 PM, Ch Ba wrote:

> So I have a piece of code that I didn't write a spec for, and now rcov
> is yelling at me about it. The problem is that I'm not really sure  
> how I
> should do it.
>
> def build_structure(paths)
>  unless File::exists?('specdoc')
>    Dir.mkdir('specdoc')
>  end
>  paths.each do |path|
>    FileUtils.makedirs("specdoc/#{strip_file(path)}")
>  end
> end
>
> I want to make sure I have good coverage, but should I just come up  
> with
> some random paths, make it make them and then delete them? I just  
> don't
> know how to come at this one to get a good spec. Any ideas?
> -- 


first off, specdoc needs to be parameterizable - for instance

def build_structure *args

   options = args.pop if args.last.is_a?(Hash)
   paths = args.flatten.compact

   root = Namespace.root

end

which sets you up to be able to do

Namespace.root = 'test/specdoc'

also, the method could return the directories created, which helps  
testing a good deal.

some ideas...

a @ http://codeforpeople.com/
--
we can deny everything, except that we have the possibility of being  
better. simply reflect on that.
h.h. the 14th dalai lama