Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The immediate problem you're having is how you're setting up your tests. The subject is being set as the unsaved instantiation of the object. If you were to do a <code>before { subject.reload }</code> after your <code>@user.save</code> then it would fix this. That's really just a bandaid.</p> <p>The real problem is you're <strong>over complicating</strong> your spec. Your setting the same user in three different places in three different ways in three different states. This should never happen.</p> <p>Here's how I'd set this up:</p> <pre><code>require 'spec_helper' describe User do describe "#authenticate" do let(:user) { User.new(name: "Example User", email: "user@example.com", password: "foobar", password_confirmation: "foobar") } it "has a valid password" do user.authenticate("foobar").should be_true end it "has invalid password" do user.authenticate("invalid").should be_false end end end </code></pre> <p>Just a couple of notes to keep in mind.</p> <p><strong>Create as few objects as possible:</strong> The more you create the more likely something isn't needed or is in a bad state and your tests fail or even worse your tests are fragile and fail unexpectedly.</p> <p><strong>Single line <code>it</code> is fine, but limiting:</strong> Single line <code>it</code> blocks are great when you need to do some quick validation, but you should use them sparingly. If you find that you're wrapping an <code>it</code> block in a <code>describe</code> then get rid of that <code>describe</code></p> <p><strong>Keep it simple:</strong> Try not to front load your tests. When you front load more than likely you're writing tests that conform to the data.</p> <p>There a bunch of other great tips over at <a href="http://betterspecs.org/" rel="nofollow">http://betterspecs.org/</a>. By no means take this as law, but it does have some good information on setting a really good foundation for writing specs.</p> <p>Lastly, good luck and enjoy writing specs!</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy rspec is getting different results from similar console operations? (M. Hartl Ruby on Rails tutorial 2ed - Section 6.3.4)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEric C
    1. USEric C
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy rspec is getting different results from similar console operations? (M. Hartl Ruby on Rails tutorial 2ed - Section 6.3.4)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you for a reply, I will play around with my tests and see what happens. Great link too, thanks for sharing it, I'd thumb-up your replay but my rep is still too low :(
      singulars
      1. PO
      1. USDmitry Matveev
 

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