Add to do project

Author: lindsey

.rspec

@@ -0,0 +1 @@
+--require spec_helper

Gemfile

@@ -0,0 +1,5 @@
+source 'https://rubygems.org'
+
+gem 'sinatra'
+gem 'pg'
+gem 'launchy'

Gemfile.lock

@@ -0,0 +1,30 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.7.0)
+      public_suffix (>= 2.0.2, < 5.0)
+    launchy (2.4.3)
+      addressable (~> 2.3)
+    mustermann (1.0.3)
+    pg (1.1.4)
+    public_suffix (4.0.1)
+    rack (2.0.7)
+    rack-protection (2.0.7)
+      rack
+    sinatra (2.0.7)
+      mustermann (~> 1.0)
+      rack (~> 2.0)
+      rack-protection (= 2.0.7)
+      tilt (~> 2.0)
+    tilt (2.0.10)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  launchy
+  pg
+  sinatra
+
+BUNDLED WITH
+   2.0.2

README.md

@@ -0,0 +1,29 @@
+# TodoList App
+
+Getting started:
+
+```
+   cd to-do-list-db
+   psql -f db/migrations/01_create_todolist_table.sql
+   psql -f db/migrations/02_create_todolist_test_table.sql
+   rspec
+```   
+
+There is a green feature test that can view a list of todo items
+
+There is a failing feature test which (when green) can insert
+a new todo item from the browser and then displays the list of
+all the todo lists
+
+### Step 1
+Implement the code to make the failing test green.
+
+You will need to think about how to add data from the browser and how to store this in the database. You will also need to think about what unit tests you need to write. 
+
+### Step 2
+Add this feature. Remember to write a feature test
+
+```
+  As a user I would like to be able to set an optional deadline on
+  my to do items
+```

app.rb

@@ -0,0 +1,12 @@
+require 'sinatra/base'
+require_relative 'lib/todo.rb'
+
+class TodoListApp < Sinatra::Base
+  get '/' do
+    "hello world"
+  end
+  get '/todos' do
+    @items = Todo.all
+    erb :todos
+  end
+end

config.ru

@@ -0,0 +1,3 @@
+require_relative 'app.rb'
+
+run TodoListApp

db/migrations/01_create_todolist_table.sql

@@ -0,0 +1,5 @@
+CREATE DATABASE TodoList;
+\c todolist;
+CREATE TABLE Todo(id SERIAL PRIMARY KEY, title VARCHAR, body VARCHAR);
+INSERT INTO TODO (title, body) VALUES ('Today', 'Buy milk');
+

db/migrations/02_create_todolist_test_table.sql

@@ -0,0 +1,3 @@
+CREATE DATABASE TodoList_test;
+\c todolist_test;
+CREATE TABLE todo(id SERIAL PRIMARY KEY, title VARCHAR, body VARCHAR);

lib/todo.rb

@@ -0,0 +1,24 @@
+require 'pg'
+class Todo
+
+  attr_reader :title, :body
+
+  def initialize(title, body)
+   @title = title
+   @body = body
+  end
+
+  def self.all
+    if ENV['RACK_ENV'] == 'test'
+      conn = PG.connect(dbname: 'todolist_test')
+    else
+      conn = PG.connect(dbname: 'todolist')
+    end
+   rows = conn.query("SELECT * FROM TODO;")
+   conn.close
+   rows.map { |r|
+    Todo.new(r["title"], r["body"])
+   }
+  end
+
+end

spec/features/helloworld_spec.rb

@@ -0,0 +1,10 @@
+require 'capybara/rspec'
+
+feature "app" do
+ 
+ scenario 'can call the index page' do 
+  visit("/")
+  expect(page).to have_content("hello world")
+ end
+
+end

spec/features/todolist_spec.rb

@@ -0,0 +1,32 @@
+require 'capybara/rspec'
+require 'pg'
+feature 'it can render todo items' do
+  before(:all) do
+    conn = PG.connect(dbname: 'todolist_test')
+    conn.exec("INSERT INTO TODO (title, body) VALUES ('Things', 'Buy stamps');")
+    conn.close
+  end
+  scenario 'visiting the page should show me a success response' do
+    visit("/todos")
+    expect(page.status_code).to eq(200)
+  end
+
+  scenario 'visiting the page should show me a todo items' do
+    visit("/todos")
+    expect(page).to have_content ('Buy stamps')
+  end
+
+  scenario 'I can add a new todo item' do
+    visit("/todos")
+    fill_in('title', :with => 'Today')
+    fill_in('body', :with => 'Fill out taxes')
+    click_button('submit')
+    expect(page).to have_content ('Fill out taxes')
+  end
+
+  after(:all) do
+    conn = PG.connect(dbname: 'todolist')
+    conn.exec("TRUNCATE TABLE TODO;")
+    conn.close
+  end
+end

spec/spec_helper.rb

@@ -0,0 +1,105 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+require 'capybara'
+require 'capybara/rspec'
+require 'rspec'
+require './app.rb'
+Capybara.app = TodoListApp
+ENV['RACK_ENV'] = 'test'
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

views/todos.erb

@@ -0,0 +1,6 @@
+<% for @item in @items %>
+  <li>
+     <%= @item.title %>
+     <%= @item.body %>
+  </li>
+<% end %>