From: David Chelimsky <dchelimsky@...>
Date: 2007-02-08T13:10:09+09:00
Subject: Re: Accessing helper module constants in rspec contexts.

On 2/7/07, Tekhne <peter.havens@gmail.com> wrote:
> I'm trying to learn rspec, and came across something unexpected with
> the following code. A little googling hasn't turned any answers up so
> far...
>
> module TestHelper
>   CONSTANT = "constant"
> end
>
> context "A context" do
>   include TestHelper
>
>   specify "should allow unqualified access to included constants" do
>     CONSTANT.should_eql "constant"
>   end
>
>   specify "should allow qualified access to all constants" do
>     TestHelper::CONSTANT.should_eql "constant"
>   end
> end
>
> ...I would expect both specifications to pass since I think that's the
> way Ruby itself behaves when using include (you get direct access to
> constants in the local scope when included, right?), but the
> unqualified specification fails. Is this a bug in rspec, a "feature"
> of rspec, a mistake on my part, or something else?

It's a known bug in rspec:

http://rubyforge.org/tracker/index.php?func=detail&aid=7613&group_id=797&atid=3152

Thanks for posting this - you may have actually shed some light on the
problem by posing the qualified and unqualified references.

Cheers,
David

>
>
>