Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby Build a Todo List Application with Rails 4 Build a Todo List Application with Rails 4 Editing Todo Lists

Robin Malhotra
Robin Malhotra
14,883 Points
Posted by Robin Malhotra
Robin Malhotra
14,883 Points

So, why are we doing this again?

I'm a big fan of TDD and stuff, but I would really appreciate if we could start with building a simple app and THEN do all the testing pizazz later. It really throws me off as a beginner.

Thanks.

Kenan Xin
Kenan Xin
16,139 Points
Kenan Xin
Kenan Xin
16,139 Points

i totally feel the way, it is like if there is a missing bridging course in the path. I couldn't understand what was i typing and what each symbol, methods mean, like options[:title] || = "this is my todo list." why there is a ":" symbol and whats the || for?

Robin Malhotra
Robin Malhotra
14,883 Points
Robin Malhotra
Robin Malhotra
14,883 Points

Exactly @Kenan. I've actually left Ruby completely after the video, though I'll get back (maybe I'll do Joy's Ruby API course?)

3 Answers

Robin Malhotra
Robin Malhotra
14,883 Points
Robin Malhotra
Robin Malhotra
14,883 Points

Okay, so after roughly 3 months(!) I've finally restarted my efforts with this course. I still agree with @Kenan Xin that there be a is 'bridge course' missing in the rails track. So, I've referred to some extra resources, and a lot of things make more sense now. This particular chapter was very helpful:-

https://www.railstutorial.org/book/toy_app

Andrew Gay
Andrew Gay
20,893 Points
Andrew Gay
Andrew Gay
20,893 Points

From what I have heard it is better practice to write the tests first rather than the application.

I found this response/question from stackoverflow seems to provide some decent information on TDD, specifically this line:

"It saves time really. If you like labyrinth puzzle, you know it is almost always easier to solve it if you go from finish to start. Same with TDD. Without Test Driven you are consistently thinking 'what should i do next'. With Test Driven, the test will tell you what to do next (it breaks if the logic is not there so you just need to fix the broken part). Also you have less bugs which will save you a lot of time in the long run."

Though to every left there is a right, and I have seen others say quite the opposite. I would suggest to continue to develop the tests first just to ensure you application is functioning properly.

These simple applications might not make to much sense, but once you start developing major application I would venture to say it would make more sense to have a better understanding on how your project works and if it Actually works by writing the tests first.

andyphan
andyphan
3,082 Points
andyphan
andyphan
3,082 Points

Because if you can't test things, then it would be harder to build a application.