Scaffold Currents

Create base scaffold for Currents. Exclude .js and .css assets created
since they won't be used (hopefully).
Add associations to Models

Add ActiveRecord associations to User, Idea, and Current models.
Create migration for adding Currents to schema

Migration adds the Currents table and a column in ideas to reference a
current the idea belongs to.
Run Currents migration to update schema
Condense Currents view specs into one file
Change Currents helper pending spec message
Move Currents request spec and add pending spec
Add validations to Currents model

Validates:
  * presence and uniqueness of a title
  * presence of a description and owner id
  * the user record specified as the current owner
Specify partial form to render in Current views

Specify that the 'currents/_form' partial should be rendered with the
'edit' and 'new' views when working with Currents.
Change comment notes in Currents controller

Change the comments mentioning routes with an 'id' in them to conform
to 'current/:id' instead of 'current/1' for readability and easy
matching with output created by 'rake routes.'
Add strong params placeholder for Currents

Add placeholder for specifying Current strong parameters in the
Currents controller.
Fill in Currents factory

Fill in fields required by Currents to be generated in the spec
factory.
Use FactoryGirl to generate Current records

Instead of stubbing records to test in the Current views, use the
Currents factory to generate records.
Specify templated for rendering in Currents specs

Specify which templates are to be rendered in the Currents view specs.
By moving all view specs into the same file, rspec tries to find a view
called 'CurrentsViews' when simply calling 'render.' In order to test
all the views in one file, the template to be rendered needs to be
passed as an argument to the 'render' method.
Hack a matcher for 'currents/edit' spec

'current_path' can't be passed an argument for some reason. Using this
silly hack temporarily.
Fix Currents controller expectation syntax

Use 'expect...to' instead of '...should' syntax when specifying what
the results of the tests are expected to be.
Use factory to create Current records

Use the FactoryGirl factory for Currents to create records instead of
creating them with any hard-coded values set in 'valid_attributes.'
Test Currents controller 'POST' with temp attributes

Currents controller spec is still not passing. Use 'build(:current)'
instead of 'valid_attributes' when testing POST actions.
'valid_attributes' is still unimplemented and may not be used if the
controller can be tested entirely by data generated from the factory.

Four tests currently fail with the following errors:

  * CurrentsController POST create with valid params assigns a newly
    created current as @current
      - Failure/Error: expect(assigns(:current)).to be_persisted
          expected persisted? to return true, got false

  * CurrentsController POST create with valid params creates a new
    Current
      - Failure/Error: expect {
          count should have been changed by 1, but was changed by 0

  * CurrentsController POST create with valid params redirects to the
    created current
      - Failure/Error: expect(response).to redirect_to(Current.last)
          Expected response to be a <redirect>, but was <200>

  * CurrentsController GET show assigns the requested current as
    @current
      - Failure/Error: expect(assigns(:currents)).to eq([current])

          expected: [#<Current id: 10, title: "A quasi dignissimos
          optio vitae autem adipisci.", description: "Vel omnis nam.
          Nostrum praesentium dolor velit. Sed...", owner_id: 101,
          created_at: "2014-04-08 01:17:38", updated_at: "2014-04-08
          01:17:38">]
               got: nil

       (compared using ==)