Added: 1 year ago
From: UserGroupsatGoogle
Views: 7,550
Sort by time | Sort by thread (beta)

Link to this comment:

Share to:

All Comments (4)

Sign In or Sign Up now to post a comment!
  • Thanks, good video to start TDD.

  • Ok, here is where I think Rails & TDD clash: What do you do when you decide "ok, I need a scaffolding with a controller and model etc" Do you generate a scaffold (and also a migration) with 1 field & then continually write more & more migrations for just one field or updating just one field? That doesn't make sense to me. I think there needs to be a little bit of balance here so if it were I would write all of the tests for 1 model and THEN product the scaffolding (or whatever) and go from there

  • @DJTripleThreat78 Short answer - don't use scaffolds.

    The longer answer is that by writing unit and integration tests, along side of the code that it takes to pass them, slowly, line by line, you learn what you are doing and are able to engineer better application code than you ever will be able to by creating scaffolds and perhaps looking back at the code.

  • @m3talsmith thanks for that. I'm actually working on a rails project this weekend so I will keep this in mind.

Loading...
Alert icon
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more