title: Why are the RSpec tests placed within the `module` keyword?
body: <p>First, I'm not attempting to test a module. I'm testing classes within a single module. <a href="https://stackoverflow.com/questions/19205352/testing-a-class-inside-of-a-module-with-rspec">This SO question/answer</a> doesn't describe the code I'm looking at, so it's tough to draw parallels to my curiosity. </p>
  
  <p>I'm following along <a href="https://codequizzes.wordpress.com/2013/10/25/creating-a-tic-tac-toe-game-with-ruby/" rel="nofollow noreferrer">with this tutorial</a>, which is outdated; However, it's a suggested resource. </p>
  
  <p>My specific question is: </p>
  
  <p>Why is the RSpec language in the spec file placed within the <code>module TicTacToe</code>, like so:  </p>
  
  <pre class="lang-rb prettyprint-override"><code>require 'some_file'
  
  module TicTacToe
    #RSpec examples here
  end
  </code></pre>
  
  <p>I'm very new to RSpec and coding in general, so I'm not familiar with the conventions of writing tests in RSpec; Is this organization necessary? Out-dated? My tests are passing and things are working as expected; I'm just attempting to learn how to write tests, and most specs begin with <code>RSpec.describe Foo do</code> or <code>describe Bar do</code></p>