-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with ci_reporter and Rails 4 #106
Comments
I do have the same issue. Have not found a solution yet. |
I'm using minitest-reporters as a workaround. Just include it on your Gemfile and add the following to your
|
Perfect. This works flawlessly with my rails4 app! Thanks. |
Same issue here (Rails 4.0.3) |
Same issue. Thank you for the fix @pbendersky. |
I'm seeing the same issue with Test::Unit. Does anyone know of a fix yet for that? I'm willing to dig deeper if someone could get me started on where to look. I'm getting no output and no error so I'm not sure where to start. |
Got it working with:
which is more or less: |
Thanks for the tip retoo. I initially put require "ci/reporter/rake/minitest_loader" in test_helper.rb which caused it to run locally too and I didn't mind that until I noticed it swallowing up my debug output statements (puts etc). Now, I'm using your command to have only jenkins run the ci_reporter xmls. |
We are in the process of cleaning out old issues. Specifically, the |
Closing due to inactivity. |
Guys, got it working with current version by hooking to the test rake task instead of minitest like: task :test => 'ci:setup:minitest' |
I've created a new Rails 4 app and would like to use ci_reporter for testing. However, after running 'bin/rake ci:setup:minitest test', my tests pass but the report files are not being generated. When I roll my app back to Rails 3.2.12 it seems to work fine. Is there a known issue with Rails 4?
The text was updated successfully, but these errors were encountered: