Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Ruby Build a Todo List Application with Rails 4 Build a Todo List Application with Rails 4 Viewing Todo Items: Part 1

David Forero
David Forero
5,492 Points

Terminal in Mac does not back trace errors when testing

Hello,

When following the course step by step I get a notification message:

If you need more of the backtrace for any of these deprecations to identify where to make the necessary changes, you can configure config.raise_errors_for_deprecations!, and it will turn the deprecation warnings into errors, giving you the full backtrace.

I see that Jason's test results include a section "Failures" that my test results does not contain.

I have tried adding the config.raise_errors_for_deprecation inside the config folder but I can't get it to look like Jason's.

Thank you

1 Answer

Maciej Czuchnowski
Maciej Czuchnowski
36,437 Points

This message only applies to deprecations - changes in rspec syntax between Jason's version and your version. In other words: this will only tell you more about what is old and why in the syntax that Jason is using.

You should see all the relevant failures and passes higher up, just scroll the console up.

Maciej Czuchnowski
Maciej Czuchnowski
36,437 Points

You would have to use the exact same version of rspec to use Jason's code and not get deprecation warnings or 'true' value errors (when you see an error that 'true is comparing to true?' or something similarly confusing, just change the be_true in specs to be_truthy and be_false to be_falsey).