@dbugger was 100% correct on this -- it was an orphaned fixture. My mistake was assuming the errors had something to do with the controller and model code, not the seeding process Rails goes through when populating the test database.