There should be a rake task which only generates the report.
I use route_dog in my CI run managed by Jenkins. The report file gets archived and published on the project page. So there's no need to open it (especially on the headless server). However, I have launchy in my Gemfile (I use it for capybara) so it gets required and tries to launch a browser, failing. I had to stub Lunchy::Browser.run method.
It would be also clever to allow explicit setting of report filename and path, e.g. through ENV.
If you agree with me here, I could come up with a pull request.
There should be a rake task which only generates the report.
I use route_dog in my CI run managed by Jenkins. The report file gets archived and published on the project page. So there's no need to open it (especially on the headless server). However, I have launchy in my Gemfile (I use it for capybara) so it gets required and tries to launch a browser, failing. I had to stub Lunchy::Browser.run method.
It would be also clever to allow explicit setting of report filename and path, e.g. through ENV.
If you agree with me here, I could come up with a pull request.