Class variable state leaked/persisted between examples

[francktrouillez]

Class variable state leaked/persisted between examples

[pirj]

Detecting and revering changes on a vast number of class objects in the object space, global variables, constants etc between each example is hard if even possible, error-prone and would have an insane overhead.

If you need isolation, use https://github.com/rspec/rspec-support/blob/8cbf7f9aecbefacd74da16ec2e713358ff72925b/lib/rspec/support/spec/in_sub_process.rb
Check https://github.com/search?q=org%3Arspec%20in_sub_process&type=code for usage examples.

[francktrouillez]

Thanks for the quick answer! I was indeed expecting this, but wanted to make sure, in case I missed something.

Thanks!

[JonRowe]

This is an example of global state and we can't make any atttempt to reset this for you but I can suggest some approaches to help test it:

You can add a "reset" to this global state and call it between each spec in a hook, we actually do this ourselves in places.

You could also change how this state is encapsulated and instead of using multiple class variables you have a normal instance of a class which you test, but then have a single "class instance" of this class in reality, you can see an example of this with our "RSpec::World".