Databases
StackOverflow2013
Postsdbo
POAdding rspec test for library module doesn't seem to pickup Expectations and Matchers
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAdding rspec test for library module doesn't seem to pickup Expectations and Matchers
    primarykey
    data
    text
    <p>I'm adding more rspec testing to my app and would like to test a ScoringMethods module, which is in /lib/scoring_methods.rb. So I added a /spec/lib directory and added scoring_methods_spec.rb there. I required spec_helper and set up the describe block as so: </p> <pre><code>require File.expand_path(File.dirname(__FILE__) + '/../spec_helper') describe ScoringMethods do describe "should have scorePublicContest method" do methods = ScoringMethods.instance_methods methods[0].should match(/scorePublicContest/) end end </code></pre> <p>Now <code>methods[0]</code> is a String and there is no problem matching the public method name with the regular expression. And the relative path to "spec_helper" is correct.</p> <p>The problem is that the entire setup doesn't seem to use the rspec library. Running the example yields:</p> <pre><code> ./spec/lib/scoring_methods_spec.rb:7: undefined method `match' for Spec::Rails::Example::RailsExampleGroup::Subclass_1::Subclass_1:Class (NoMethodError) ... </code></pre> <p>The entire Expectation and Matcher support seems to be missing. To test my supposition, I changed a working helper spec by replacing "is_instance_of" to "is_foobar_of". That test simply fails and says "is_foobar_of" is not a method of the targeted object; that it, this entire Spec::Rails::Example... hierarchy isn't present.</p> <p>I've tried using other matchers as well. I've tried "be_instance_of" and some others. It seems that I'm not including the rspec library properly.</p> <p>Finally, ScoringMethods is a module, just the same way Helpers are modules. So I thought that it would be possible to test a module (as opposed to classes, such as Controllers and Models).</p> <p>I'd greatly appreciate your thoughts on what I've done wrong. Perhaps there is a more effective way of testing library modules? Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USPeter Degen-Portnoy
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAdding rspec test for library module doesn't seem to pickup Expectations and Matchers
      1. USdgilperez
      1. VTFavorite
    2. VO
      singulars
      1. POAdding rspec test for library module doesn't seem to pickup Expectations and Matchers
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAdding rspec test for library module doesn't seem to pickup Expectations and Matchers
      1. USJeremy Smith
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload