It can be difficult to test the different scenarious for a module intended for use by including in another class.
If the class is statically defined in the spec, any later definitions extend, not replace, the first definition - which can cause test issues and breaks isolation between examples.
RSpec.describe SomeModule do
class SomeIncluder
include SomeModule
end
| #!/bin/sh | |
| # Install brew | |
| /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" | |
| # Apple hides old versions of stuff at https://developer.apple.com/download/more/ | |
| # Install the latest XCode (8.0). | |
| # We used to install the XCode Command Line Tools 7.3 here, but that would just upset the most recent versions of brew. | |
| # So we're going to install all our brew dependencies first, and then downgrade the tools. You can switch back after | |
| # you have installed caffe. | |
| # Install CUDA toolkit 8.0 release candidate | |
| # Register and download from https://developer.nvidia.com/cuda-release-candidate-download |
| ... | |
| gem 'kaminari' | |
| gem 'ransack' | |
| .. |