Closed liam-ngy closed 8 years ago
Hey @hnguyen94,
Thanks for reporting!.
This error has been usually happening when something not expected is being returned in the output for the RSpec test runner, which should be in json. One of the cases that we have seen, is using simplecov, that also returns the output when the formatter is json making the output invalid.
If you have time and it's possible, I would love to see the output of rspec, to see if there is anything strange that is causing this behaviour. Should be similar to:
Open a terminal cd project_directoy rspec --format=json spec/file_that_failed_spec.rb
That way, I could inspect the output and see if there is something strange there. Anyway, I'm really expecting to release very soon a new version with a sanitization of the RSpec output.
Thank you!
Hey @hnguyen94,
I have released an update for the package that is supposed to fix this issue. Please, give it a go whenever you have time and let me know how it goes. I close this issue, but do not hesitate to reopen if it is still failing.
Thanks for reporting again!.
[Enter steps to reproduce below:]
Atom Version: 1.5.3 System: Mac OS X 10.11.4 Thrown From: rspec-tree-runner package, v0.2.0
Stack Trace
Uncaught SyntaxError: Unexpected token s
Commands
Config
Installed Packages