Forum Discussion
Hi!
Could you please use the `code` feature of the forum - in the toolbar, [...](expand) then [</>](insert code sample) - for better readability?
Your issue seems related to omniauth more than cucumber. You seem to already have looked at their documentation here: https://github.com/omniauth/omniauth/wiki/Integration-Testing#mocking-failurehttps://github.com/omniauth/omniauth/wiki/Integration-Testing#mocking-failure
Did you notice the following part?
By default Omniauth will raise an exception for invalid credentials in the development and test environments. If you'd like to be redirected to the/auth/failure
endpoint in those environments, include this code:OmniAuth.config.on_failure = Proc.new { |env| OmniAuth::FailureEndpoint.new(env).redirect_to_failure }
For debugging, which IDE are you using?
If you are using VS Code, make sure to have `debase` and `ruby-debug-ide` gem installed and the ruby extension for VS Code properly set-up. You'll then have the possibility to have such things in your `launch.json`
{
"version": "0.2.0",
"configurations": [
{
"name": "Cucumber",
"type": "Ruby",
"request": "launch",
"useBundler": true,
"cwd": "${workspaceRoot}",
"program": "${workspaceRoot}/bin/cucumber",
"internalConsoleOptions": "openOnSessionStart"
},
{
"name": "Cucumber current feature file",
"type": "Ruby",
"request": "launch",
"useBundler": true,
"cwd": "${workspaceRoot}",
"program": "${workspaceRoot}/bin/cucumber",
"args": ["${file}"],
"internalConsoleOptions": "openOnSessionStart"
}
]
}
Thanks for your reply. Yes, I have incorporated the additional code as well, but I wasn't positive about where it went. I tried several different options, but none seem to work.
Thanks for pointing out where to find the 'code' option.
I have edited my original post to reflect your suggestions. My IDE is Codio, and I'm using byebug for debugging