Reputation: 27114
A lot of times I'll have a breaking test.
So I'll go to the test, and right before the line that breaks, I'll throw in a debugger.
Let's see what it's about to do to, right?
But when my app hits the debugger. And I hit s
or step
, it makes the tiniest little insignificant steps. Literally, I'll be hitting the same thing forever and still not make it closer to my objective which would be the next code that I wrote, not how Ruby parses it, or how the ApplicationController runs on a rudimentary level.
Am I missing some important detail here? Or is this how everyone uses debugger?
My apologies if this is an idiot question.
Upvotes: 1
Views: 63
Reputation: 703
You can juste type continue
in the console in order to continue to the next break point or to the end of the process. http://guides.rubyonrails.org/debugging_rails_applications.html#resuming-execution
Upvotes: 3