Databases
StackOverflow2013
Postsdbo
POWhy is my Rspec test on length validation failing ? (rails/guard/rspec)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is my Rspec test on length validation failing ? (rails/guard/rspec)
    primarykey
    data
    text
    <p>I have a very simple test on a Deal model that keeps failing and I can't understand why. </p> <p>My Deal model:</p> <pre><code>class Deal &lt; ActiveRecord::Base belongs_to :admin_user, :foreign_key =&gt; 'admin_user_id' attr_accessible :url_path, :country, :title, :description, :twitter_msg, :image_url, :prelaunch_date, :deal_launch_date, :deal_end_date, :featured, :admin_user_id :as =&gt; :admin_user validates :title, presence: true, length: { maximum: 200 } </code></pre> <p>The test:</p> <pre><code>require 'spec_helper' describe Deal do let(:admin_user) { FactoryGirl.create(:admin_user) } before(:each) do @attr = { url_path: "lorem ipsum", country: "France", title: "lorem ipsum", description: "lorem ipsum lorem ipsum lorem ipsum lorem ipsum lorem ipsum lorem ipsum", twitter_msg: "lorem ipsum", image_url: "lorem ipsum", prelaunch_date: 1.days.from_now.change(hour: 10), deal_launch_date: 3.days.from_now.change(hour: 10), deal_end_date: 15.days.from_now.change(hour: 10), featured: true, admin_user_id: 1 } </code></pre> <p>end</p> <pre><code>describe "tests on deal models validations for TITLES" do it { should validate_presence_of(:title) } it { should_not allow_value(" ").for(:title) } it "should reject deals with title that is too long" do long = "a" * 201 hash = @attr.merge(:title =&gt; long) Deal.new(hash).should have(1).error_on(:title) end end </code></pre> <p>and the test fail with "Deal tests on deal's models validations for TITLES should reject deals with title that is too long Failure/Error: Deal.new(hash).should have(1).error_on(:title) expected 1 error on :title, got 2 => <strong>i don't get why i have 2 errors</strong>. i should get only one and my test would be passing!</p> <p>The strangest thing: - when I do <code>rspec spec</code> it fails - then if I change in my validates the number of characters to 195 and in my test to 196, it then passes - but then, the next time I relaunch guard or my server, then it fails again and if I change again to 190 and 191, it then works again, but as soon as I restart guard or my server</p> <p>I tried this many times and it's always the same problem. I don't understand, it seems guard or my server is the problem.</p> <p>Does anybody have a clue to why it happens and how I can correct this?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmeagar
    1. USMathieu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is my Rspec test on length validation failing ? (rails/guard/rspec)
      1. USgotva
      1. VTFavorite
    1. COpost your `spec_helper.rb` as well. I think the problem is there. Something loads your model twice and this adds the same validation. Two validations adds two errors.
      singulars
      1. POWhy is my Rspec test on length validation failing ? (rails/guard/rspec)
      1. USgotva
    2. COYou might want to print out the two errors as well
      singulars
      1. POWhy is my Rspec test on length validation failing ? (rails/guard/rspec)
      1. USPeter Alfvin
    3. CO@gotva sorry for delay, i updated the question with my spec_helper file
      singulars
      1. POWhy is my Rspec test on length validation failing ? (rails/guard/rspec)
      1. USMathieu
 

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