If I have a .simplecov file, then when I run RAILS_ENV=test rake db:schema:load, I get a coverage report.
If I move the code from .simplecov to my test_helper.rb file (I use MiniTest), this does not happen.
I expect that this should never happen - loading the schema in the test environment is not a coverage test.
The reason this is annoying is that it causes my schema to load on CircleCI, generates a coverage below my threshold, and then fails the build.
I probably posted this question before a recent change to the simplecov readme... the change I needed to avoid this problem was to update my Gemfile to turn off auto-requiring of the simplecov gem:
gem 'simplecov', require: false
I then explicitly added Simplecov to my test/test_helper.rb as recommended in the README and that fixed this problem.
Related
I have TeamCity up and running in a mac environment. A trigger is also setup to to run a rake task containing a number of test cases on every git commit. The rake command successfully pulls the code and runs the test cases. The passing test cases are shown correctly in the TeamCity interface, however, the failing test cases do not show up and the build is marked as successful. When I look at the error Build Log, failing tests are shown as errors. The question is why TeamCity is interpreting failing tests as errors and not as actual failing tests?
The assertions are as simple as the following (obvious failure):
test 'simple_test' do
a = 14
ssert_equal 341, a
ends
PS: the check box to fail the build upon at least one test fail is turned on in Failure Conditions(i.e. at least one test failed)
Ruby version = 2.2.2,
Rails version = 4.2.1,
TeamCity version = 9.1.1,
Testing framework = minitest,
Here is the build log output
Teamcity is not picking up failed tests because mini-test reporter is not up and running. To fix this, following gems must be present in the Gemfile:
gem "minitest", :group => :test
gem 'minitest-reporters', :group => :test
Also minitest reporter must be called. The best place to call it is test_helper.rb
require 'minitest/reporters'
MiniTest::Reporters.use!
My Rails app that I am upgrading to 4.2 from 3.2 has strange behavior in regards to the asset pipeline.
The guide says to use: RAILS_ENV=production bin/rake assets:precompile which causes this error:
Sass::SyntaxError: $red: "CC" is not a number for `rgba'
(sass):86
ArgumentError: $red: "CC" is not a number
The --trace doesn't point to any of my files and odder still is that I don't have any sass files to begin with.
I ran it without the RAILS_ENV and it compiled without complaint and everything seems to work.
My app has multiple layouts and themes which made for a slightly more complex and verbose set of asset manifests.
My question is, even though it seems to work is using that rake task without the RAILS_ENV=production going to cause issues?
It looks like you are actually sending an incorrect value to the sass compiler. Grep the code for $red or rgba and enter a correct list of numbers for the rgba statement that is causing the error.
I have a Rails 4 application, tested with stock minitest. Zeus is set-up and working, so is Guard.
However, when I have Zeus running and fire Guard, it does not speed up: Guard does not seem to use Zeus for faster booting, despite having
guard 'minitest', :zeus => true do
end
in the guardfile. Is this simply not (yet) supported in Rails4? Am I missing some crucial bit of configuration?
Some additional details: when I run my tests with zeus rake test they are slow; comparable to running them without zeus rake test. When running with zeus test test/ they are ten times faster, but they run twice (a known issue, yet maybe a hint to what I am doing wrong?). Also not that I fire up Guard with bundle exec guard, because that is what Guard tells me to do.
Try using spring. https://github.com/jonleighton/spring
Add this to your gem file:
gem "spring"
Run bundle install.
Use this for your Guardfile:
guard "minitest", all_on_start: false, spring: true do
Remember the first time you run guard it will take the normal amount of time because it is loading the environment. After the first run it will significantly increase the loading speed.
For some reason, I was using a really old guard and guard-minitest 0.4.x. Updating them to the current 2.x.x version solves my issues.
Zeus has a known issue where it runs specs double if you include the default "autorunner" for a testing suite.
It is common to see tests running twice when starting out with Zeus.
If you see your tests/specs running twice, you should try disabling
require 'rspec/autotest' and require 'rspec/autorun' (for RSpec), or
require 'minitest/autorun' (for Minitest). (see #134 for more
information).
https://github.com/burke/zeus#important
However, Rails4 minitest includes "rails/test_help" which is a file in Railties 4.0.0; which includes yet another custom runner. And does other generic of setup and configuration.
For Rails4 with default minitest, there is no simple include to leave out, it seems.
Is there a solution for this?
i was just facing this same problem with Rails4+minitest+zeus.
After i include gem "minitest-rails-shoulda" in my Gemfile, zeus starts to run tests twice.
I just changed the gem orders at Gemfile and it solves!
Gemfile with Zeus running twice:
group :test do
gem "minitest-rails-shoulda"
gem 'minitest'
#...
end
Gemfile CORRECT:
group :test do
gem 'minitest'
gem "minitest-rails-shoulda"
#....
end
I'm working on writing simple unit tests for a Rails 3 project, but I'm unable to actually execute any tests.
Case in point, attempting to run the test auto-generated by Rails fails:
require 'test_helper'
class UserTest < ActiveSupport::TestCase
# Replace this with your real tests.
test "the truth" do
assert true
end
end
Results in the following error:
<internal:lib/rubygems/custom_require>:29:in `require': no such file to load --
test_helper (LoadError)
from <internal:lib/rubygems/custom_require>:29:in `require'
from user_test.rb:1:in `<main>'
Commenting out the require 'test_helper' line and attempting to run the test results in this error:
user_test.rb:3:in `<main>': uninitialized constant Object::ActiveSupport (NameError)
The action pack gems appear to be properly installed and up to date:
actionmailer (3.0.3, 2.3.5)
actionpack (3.0.3, 2.3.5)
activemodel (3.0.3)
activerecord (3.0.3, 2.3.5)
activeresource (3.0.3, 2.3.5)
activesupport (3.0.3, 2.3.5)
Ruby is at 1.9.2p0 and Rails is at 3.0.3.
The sample dump of my test directory is as follows:
/fixtures
/functional
/integration
/performance
/unit
-- /helpers
-- user_helper_test.rb
-- user_test.rb
test_helper.rb
I've never seen this problem before - I've run the typical rake tasks for preparing the test environment. I have nothing out of the ordinary in my application or environment configuration files, nor have I installed any unusual gems that would interfere with the test environment.
Edit March 9th
Xavier Holt's suggestion, explicitly specifying the path to the test_helper worked; however, this revealed an issue with ActiveSupport.
Now when I attempt to run the test, I receive the following error message (as also listed above):
user_test.rb:3:in `<main>': uninitialized constant Object::ActiveSupport (NameError)
But as you can see above, Action Pack is all installed and update to date.
Edit March 13th
When attempting to run tests using rake test:units the following stack trace is dumped to the console:
test/unit/bookmark_test.rb:3:in `<top (required)>': uninitialized constant Objec
t::ActiveSupport (NameError)
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5:in `load'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5:in `block in <main>'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5:in `each'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5:in `<main>'
rake aborted!
So looking into the file listed above, I see the following:
#!/usr/bin/env ruby
# Load the test files from the command line.
ARGV.each { |f| load f unless f =~ /^-/ }
To my knowledge, everything looks as expected.
Your test/test_helper file should have been created when you generated the application. It contains this valuable content:
ENV["RAILS_ENV"] = "test"
require File.expand_path('../../config/environment', __FILE__)
require 'rails/test_help'
class ActiveSupport::TestCase
# Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
#
# Note: You'll currently still have to declare fixtures explicitly in integration tests
# -- they do not yet inherit this setting
fixtures :all
# Add more helper methods to be used by all tests here...
end
The second line here is the most important: it requires the config/environment.rb file at the root of your application, which in turn requires a lot of other things, including the valuable (I like that word today, ok?) ActiveSupport constant.
When you generate a controller, model or scaffold it'll also generate tests for those. I just ran rails g scaffold ticket in my app and it generated test/unit/ticket_test.rb which contains this:
require 'test_helper'
class TicketTest < ActiveSupport::TestCase
# Replace this with your real tests.
test "the truth" do
assert true
end
end
The first line of this file will require the test/test_helper.rb file that we jut saw. This will load ActiveSupport and the TestCase class within it, thereby making this test feasible. Everything else just flows on from there.
With all that explanation out of the way (even though it's something that you already know), I'm placing a large wager on it's something that's masscaring your LOAD_PATH, causing the test directory to be removed from it.
What's really unusual is that when you do specify the full path to the test/test_helper.rb you're saying it loads it, but ActiveSupport is still undefined. Well, that should be loaded as-per the description above. Is it actually loading config/environment.rb? Can you put something such as:
puts "LOADING CONFIG/ENVIRONMENT.RB"
At the top of your config/environment.rb file and then run the tests again? It should be output. Very unusual.
Continuing on the thread about LOAD_PATH... Got a dirty little secret you're not telling us about?
Actually, Dan Cheail makes a good point. You could be running the tests using ruby test/unit/ticket_test.rb in which case test_helper wouldn't be available, but still that still doesn't explain why when you specify the full path you're still getting an undefined constant ActiveSupport.
If you want to run a single test you should be doing this:
ruby -Itest test/unit/ticket_test.rb
That -I option there adds the test directory to the load path, meaning the test_helper file will be available through a straight require 'test_helper'. If it still errors after this, I reckon your test/test_helper.rb is either empty or broken.
The problem you're having is the way you're executing tests. Simply calling ruby test/unit/user_test.rb doesn't set up the load path, which explains the problems you've been having.
rake test:units is what you want and should work straight away.
Sorry about the post here, but I am unable to comment on questions yet.
what environment are you running, Win (has an issue with a .gemspec file) Linux, Mac?
Are you using RVM?
Test-Unit is installed by default with Rails, if you installed the gem Test-Unit you will get a conflict between the 2. try uninstalling the gem and your tests should start working.
If running on windows I would gem uninstall "autotest", then navigate to the following dir
drive:\Ruby192\lib\ruby\gems\1.9.1\specifications
In here you will find .gemspec files. Ensure that you dont have 2 autotest.gemspec files or any, for that matter. if so remove(delete) them, then download and gem install the autotest gem again. Grab the latest by using version switch.
You should be able to run your autotests. I did come across this once before, so to fix I simply removed the view and helper test files and wrote everything in the standard test file. Other than that I know running on windows autotest had issues, because of the ruby installer and bundler not clearing out things correctly and forgetting files.
I will find the link for you, to better explain.