1. Do chapters 6, 7, and 8. Type all the code along with the examples and test it out. Play around with it to see if you can get different outcomes.

2. Do all the exercises. We're here to help each other so if you have questions, be sure to ask in the thread. If you can help someone out, please do!

3. Make a least one comment in this thread about something you learned, found interesting, or didn't understand very well.


There is an IRC chat at [#learnrubyonrails](http://webchat.freenode.net/?channels=learnrubyonrails) on Freenode. I plan to start averaging about an hour a day M-F hanging out in there (my access on weekends in somewhat limited but I can be on in the evenings for a bit). I encourage you to also.

5 thoughts on “[STUDY GROUP] WEEK 3!”

  1. is anyone getting left behind? I had a head start on this study group but it’s already caught up to me, don’t even know if I could get chapter 8 done by Sunday.

  2. Regarding tests, I understand that what we’re doing here is extraordinarily simple and that the tests follow suit. In more complex applications, how complex do/should the tests become? It seems that one might spend at least as much time writing tests as writing the rest of the code? Anyone know if this is the case?

  3. In Chapter 8.5 exercise 2

    Does anyone know what the best practices for decoupling the tests from the implementation? I am looking for answers in terms of file and folder organization.

    I basically built two utilities files with one module each (one file for session sign in and another for user sign up) and put them in the same folder as utilities.rb .

    It took me a while to figure out how to include the modules properly. At first I required the files and included the modules in each of my test files. But I noticed that the tests passed even if I removed the require statements. After looking at the rspec config file I noticed that all the files in the utilities folder are required.

    Finally I included each module in the appropriate test file. My tests pass and files look neat but I have no idea if I am following proper convention.

  4. Tip** If you push to Heroku and your CSS looks different than what is looks like on your localhost, there was a command I needed to run

    RAILS_ENV=production bundle exec rake assets:precompile

    then do a git add .

    git commit

    git push heroku

    this fixed my css looking different on heroku, I heard there is also a way to turn precompiling on in a config file but can’t find it yet.


Leave a Comment