Spec failing to run specs when spec.opts is present on 1.2.9

Hi

I ran across the following when running spec on an old merb app.

$ cat spec/spec.opts
$ spec spec/models/topic_spec.rb

Options written to spec/spec.opts. You can now use these options with:
spec --options spec/spec.opts
$ cat spec/spec.opts
spec/models/topic_spec.rb
$ spec spec/models/topic_spec.rb

Options written to spec/spec.opts. You can now use these options with:
spec --options spec/spec.opts
$ cat spec/spec.opts
spec/models/topic_spec.rb
spec/models/topic_spec.rb
$ spec spec/models/topic_spec.rb -b
*

Pending:

Topic should have specs (Not Yet Implemented)
./spec/models/topic_spec.rb:6

Finished in 0.004289 seconds

1 example, 0 failures, 1 pending
$ rm spec/spec.opts
$ spec spec/models/topic_spec.rb
*

Pending:

Topic should have specs (Not Yet Implemented)
./spec/models/topic_spec.rb:6

Finished in 0.048676 seconds

1 example, 0 failures, 1 pending
$

Outside of the old merb app, I wasn’t able to duplicate this issue. I
also copied the spec_helper from a newly created merb app (1.0.12)
into the old app, but the issue persisted. Perhaps a library conflict
might be to blame?

I also encoutered an even stranger issue where a single example
resulted in multiple failures i.e. a spec containing 4 examples
produced the following output
3 examples, 3 failures

6 examples, 6 failures

Both of these issues disappeared when I reverted to 1.2.8. I’ll add
more to this thread if and when I re-upgrade.

Paul

On Oct 22, 2009, at 10:28 AM, Paul C. [email protected] wrote:

spec/models/topic_spec.rb
Pending:

Outside of the old merb app, I wasn’t able to duplicate this issue. I
also copied the spec_helper from a newly created merb app (1.0.12)
into the old app, but the issue persisted. Perhaps a library conflict
might be to blame?

Merb does override some parts of rspec and we don’t have any
integration testing with merb, so it’s very likely a lib conflict.
Take a look at lib/test in merb-core if you’re interested.

On 22 Oct 2009, at 16:28, Paul C. wrote:

Outside of the old merb app, I wasn’t able to duplicate this issue. I
also copied the spec_helper from a newly created merb app (1.0.12)
into the old app, but the issue persisted. Perhaps a library conflict
might be to blame?

Hi Paul

I use Merb extensively. Can you post your spec_helper? I may be able
to help…

Ashley


http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran

On 29 Oct 2009, at 08:28, Paul C. wrote:

If I create a new merb app (1.0.12) and model and then run rake spec,
all is well. However, if I copy its spec_helper into my own app, the
problems listed above appear. So I think the source of the issue lies
somewhere else.

Have you upgraded the old app to Merb 1.0.12? If not, what version is
it on?

Ashley


http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran

Hi Paul

I use Merb extensively. Can you post your spec_helper? I may be able to
help…

Ashley

Hi Ashley

Many thanks for your offer.

If I create a new merb app (1.0.12) and model and then run rake spec,
all is well. However, if I copy its spec_helper into my own app, the
problems listed above appear. So I think the source of the issue lies
somewhere else.

Best

Paul