I'd fix this if I could, but I'm not sure where the link is supposed to go.

The link is right above the "Deliverables" section on the word "Here's".

For some reason, the 'name="commit"' parameter in the " field keeps breaking the expected params test. I removed the 'name="commit"' parameter, and it passed the test.

this test suite does not test that controller actions actually respond to form submission. you can pass tests w/o any code in create, update actions of concretes controller.

this test suite is using a global variable, $params, that is set in a before_filter of the application controller to steal form params during run of rspec.

tests to update concrete don't actually fill out any form fields to change the info about a given concrete

if you write the code to correctly update a concrete, redirect to show page, the test will fail.

expectations of tests flip test_params and expected_params such that we expect(expected_params).to eq(test_params) when test params are generated by run of test suite/dependent on user's code and expected params are hard coded by tests.

Would love to fix this myself, but I imagine you can only handle this on your end.

Two other quick things I noticed:

1. concrete_form_spec.rb lines 3-10 check for the form_for tag in a way that precludes the use of '<%= render 'form' %>' with a _form.html.rb file
   
2. search_form_spec.rb requires that there be a param key called 'q' which is a bit strange
   

The last test (line 39) in the baby_form_spec.rb only passes if you use a text_field for the "date-time" input on the form. When the form is submitted with a date_time field you get the absolute date/time (including seconds) "birth_date"=>"2014-02-14 05:00:00.000000"
The test is looking for only month/day/year.

The only way to pass this test in the current environment is to use a text_field form helper instead of date_field.

@jmburges @AnnJohn