Chapter 3

Question 1

bundle update

Answer 1

update the gems to make sure the versions match

Question 2

git mv README.rdoc README.md

Answer 2

changing the format from RDoc to Markdown using git

Question 3

git commit -am

Answer 3

(-a) all changes, (-m) message

Question 4

note*: make sure to commit everything before deploying or else you might get an error.

Answer 4

ok

Question 5

generate a controller to handle static pages names “StaticPages” with a plan to make actions for a home page and help page

Answer 5

rails generate controller StaticPages home about

Question 6

rails s

Answer 6

rails server shortcut

Question 7

rails c

Answer 7

rails console shortcut

Question 8

rails g

Answer 8

rails generate shortcut

Question 9

bundle

Answer 9

bundle install shortcut

Question 10

rake

Answer 10

rake test shortcut

Question 11

when you add a branch, what is a good next step to do?

Answer 11

push to remote repository
git status
git add -A
git commit -m “add static pages controller”
git push -u origin static-pages
subsequent pushes can omit the arguments (git push)

Question 12

why StaticPages generates static_pages_controller.rb

Answer 12

convention in rails to use snake case. (rails generator converts camelcase to snake using the underscore method)

Question 13

you generated a controller; how do you undo it?

Answer 13

rails destroy controller StaticPages home help

Question 14

undo rails generate model User name:string email:string

Answer 14

rails destroy model User

Question 15

undo bundle exec rake db:migrate

Answer 15

bundle exec rake db:rollback

Question 16

rollback all the way to beginning

Answer 16

bundle exec rake db:migrate VERSION=0

Question 17

router

Answer 17

creates the correspondence between URLs and web pages

Question 18

get ‘static_pages/home

Answer 18

maps requests for the URL/static_pages/home to the home action in the Static Pages controller. responds to GET requect

Question 19

HTTP

Answer 19

hypertext transfer protocol. basic operations: GET, POST, PATCH, DELETE (operations between client computer and a server)client: chrome, firefox, server:apache nginx.

Question 20

HTTP operations define:

Answer 20

GET used for reading data on the web (get a page).everytime you visit a page, your browser submits a GET request. POST request sent by browser wen you submit a form. in rails (POST typically used for creating things, also for updates). PATCH and DELETE: update and destroy things on the remote server.

Question 21

GET request example

Answer 21

visit a site like google.com

Question 22

POST request example

Answer 22

submit a registration form creates a new user on the remote site

Question 23

classes in rails

Answer 23

used to organize functions

Question 24

def home
end

Answer 24

in ruby, this would do nothing. but since in inherits from ApplicationController, the behavior of this method is specific to rails. when visiting URL/static_pages/home, rails looks for static pages controller and executes the code in home action, then renders a view.

Question 25

test-driven development define:

Answer 25

TTD, testing technique in which the programmer writes failing tests first, and then writes the application code to get the test to pass.

Question 26

writing automated tests has 3 main benefits:

Answer 26

1. protect against regressions, where a functioning feature stops working for some reason. 2. allow code to be refactored 3. test act as a client for the application code, helping determine its design and its interface

Question 27

when to write test first or after writng the code:

Answer 27

when test is short when desired behavior isnt clear, write application code first security: write tests first when a bug is found, write test to reproduce it and protect against regression, then write code to fix it lean against writing test for code likely to change. write tests before refactoring code,

Question 28

integration tests:

Answer 28

tests functionality across models, views and controllers (chapter 7)

Question 29

test "should get home" do get :home assert_response :success end

Answer 29

says lets test the home page by issuing a GET request to the home action and them make sure we receive a success status code in response (verifies via assertion that result is a success)

Question 30

execute rails test command

Answer 30

bundle exec rake test

Question 31

assert_select

Answer 31

lets us test for presence of a particular HTML tag (sometimes called a selector, hence the name)

Question 32

DRY

Answer 32

dont repeat yourself. remove repition in code (such as html code). becuase we have embedded ruby in our views, we can dry our code.

Question 33

embedded ruby

Answer 33

embeds ruby into a text document. often used to embed ruby code in an html document, similar to asp, jsp, and php. (.html.erb Erb is the primary template system for including dynamic content in web pages)

Question 34

provide(:title, "Home");

Answer 34

indicates that rails should call the provite function and associate the string "Home" with the label :title

Answer 35

executes the code inside, while executes it and inserts the result into the template. yield to insert the title

Question 36

application.html.erb

Answer 36

layout file allows us to factor out common structure.

Question 37

in application.html.erb layout file

Answer 37

this code is responsible for inserting the contents of each page into the layout. (converts home.html.erb to HTML and inserts it).

Answer 38

prevents cross-site request forgery (CSRF), a type of malicious web attack