What is the expected/intended behavior for the scope of class instance
variables when running multiple specs?

It appears that setting a class instance variable in one spec will
affect it in a second spec run like so:

http://gist.github.com/174018

running `spec spec1_spec.rb spec2_spec.rb`  or `spec .` from within
that directory will fail because the state of the instance variable is
maintained.

I'm investigating a case where this behavior is affecting the passing/
failing of specs based on the order they are loaded by Rake's
FileList, and am looking for a little background before I try to solve
it.
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users

Reply via email to