You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is confusing to see "Success: Tests passed." when the debugger fails to start.
Note that no error message popups in the master branch as of today (28 Aug 2021): PR #700 adds that.
What command(s) did you run when you found the bug?
For example this may happen when you click on "Debug" without opening the folder.
The error will be thrown by debuger#startDebugger
Output, stack trace or logs related to the bug
Running tool: gauge run /path/to/project/sampleProject/specs/example.spec --simple-console --hide-suggestion
Runner Ready for Debugging
Debugger listening on ws://127.0.0.1:63946/0ac3acd3-44b3-4749-abc1-54af31248055
For help, see: https://nodejs.org/en/docs/inspector
Success: Tests passed.
Describe the bug
It is confusing to see "Success: Tests passed." when the debugger fails to start.
Note that no error message popups in the master branch as of today (28 Aug 2021): PR #700 adds that.
What command(s) did you run when you found the bug?
For example this may happen when you click on "Debug" without opening the folder.
The error will be thrown by debuger#startDebugger
Output, stack trace or logs related to the bug
Versions
Gauge (Output of
gauge -v
)Node.js/Java/Python/.Net/Ruby version
Node.js 16.8.0
Operating System information
macOS Big Sur 11.5.2
IDE information
VSCode 1.59.1
The text was updated successfully, but these errors were encountered: