zhengjia

=Navigating=
    visit('/projects')
    visit(post_comments_path(post))

=Clicking links and buttons=
    click_link('id-of-link')
    click_link('Link Text')
    click_button('Save')
    click('Link Text') # Click either a link or a button
    click('Button Value')

dnagir

# RSpec 2.0 syntax Cheet Sheet by http://ApproachE.com

# defining spec within a module will automatically pick Player::MovieList as a 'subject' (see below)
module Player
	describe MovieList, "with optional description" do
		  
	  it "is pending example, so that you can write ones quickly"
	  
	  it "is already working example that we want to suspend from failing temporarily" do
		pending("working on another feature that temporarily breaks this one")

iamvery

require 'active_record'

class Foo < ActiveRecord::Base
  establish_connection adapter: 'sqlite3', database: ':memory:'

  connection.create_table :foos do |t|
    t.string :name, null: false
  end

  #has_many :bars

iamvery

source 'https://rubygems.org'

gem 'activerecord'
gem 'sqlite3'

iamvery

source 'https://rubygems.org'

gem 'activerecord', '~>4.0'
gem 'sqlite3'

raorao

Any top-level comment on pull request ought be tagged with one of four emojis:

• ❓ for a non-blocking comment that asks for clarification. The pull request author must answer the question before the pull request is merged, but does not have to wait for the comment author to re-review before merging.

• 🎨 for a non-blocking comment that proposes a refactor or cleanup. The pull request author does not have to address the comment for the pull request to merge.

• ⚠️ for a blocking comment that must be addressed before the pull request can merge. The comment's author should leave a Request Changes review, and is responsible for re-reviewing once the pull request author has addressed the issue.

• 😻 for a comment that compliments the author for their work.