How do I figure out why errors are occurring when running unit tests on app that is being upgraded from Rails 2.3 to Rails 3.0?



I've been tasked with upgrading an app from Rails 2.3.5 to 3.0.19. This also involves upgrading Ruby from 1.8.6 to 1.8.7. After this upgrade is complete and stable, the plan is then to move to Ruby 1.9 and Rails 3.2.


Gems (output from bundle install), fyi:


Using rake (10.0.3)
Using abstract (1.0.0)
Using activesupport (3.0.19)
Using builder (2.1.2)
Using i18n (0.5.0)
Using activemodel (3.0.19)
Using erubis (2.6.6)
Using rack (1.2.7)
Using rack-mount (0.6.14)
Using rack-test (0.5.7)
Using tzinfo (0.3.35)
Using actionpack (3.0.19)
Using mime-types (1.19)
Us

Related to : How do I figure out why errors are occurring when running unit tests on app that is being upgraded from Rails 2.3 to Rails 3.0?
Pass Parameters to Rails Unit Tests
Programming Languages

I was wondering if there is a way to pass arguments to individual tests in rails similar, or similar in idea, to NUnit's TestCase Attribute. Thanx


Rails unit tests: How to add my own output to unit test results
Programming Languages

When running Rails unit tests I get output specifying line numbers and methods when a test fails, e.g.:


1) Failure:
test_05_photo_tag_add_remove(TC_javascript02Test)
[./helper/helper.rb:6:in `handle_assert'
./helper/helper.rb:17:in `check_not_string'
./helper/helper.rb:134:in `check_for_ajax_remove_string'
javascript.rb:39:in `test_05_photo_tag_add_remove']:
<false> is not true.

Is it possible to dd my own text to this stack?


Thanks in advance
Peter


Heroku app not working after rails upgraded to 3.2.11
Programming Languages

I am getting this error at Heroku logs. I ve updated the rails version to 3.2.11 and then updated the bootstrap as Herokupeople have mentioned this that there are some security issues with the Rails 3.2.10. The error is as follows.


2013-01-11T18:07:53+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/commands/server.rb:46:in `app'
2013-01-11T18:07:53+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/callbacks.rb:385:in `_run_prepare_callbacks'
2013-01-11T18:07:53+00:00 app[web.1]: from /app/vendor/bundl
How do I figure out why errors are occurring when running unit tests on app that is being upgraded from Rails 2.3 to Rails 3.0?
Programming Languages

I've been tasked with upgrading an app from Rails 2.3.5 to 3.0.19. This also involves upgrading Ruby from 1.8.6 to 1.8.7. After this upgrade is complete and stable, the plan is then to move to Ruby 1.9 and Rails 3.2.


Gems (output from bundle install), fyi:


Using rake (10.0.3)
Using abstract (1.0.0)
Using activesupport (3.0.19)
Using builder (2.1.2)
Using i18n (0.5.0)
Using activemodel (3.0.19)
Using erubis (2.6.6)
Using rack (1.2.7)
Using rack-mount (0.6.14)
Using rack-test (0.5.7)
Using tzinfo (0.3.35)
Using actionpack (3.0.19)
Using mime-types (1.19)
Us
Upgraded from Rails 2.3.4 to 2.3.14 and now tests are failing (Shocking, I know)
Programming Languages

The problem seems to be with all tests that do POST, PUT, DELETE requests. It seems that csrf token is not being attached with those requests. Thus I get redirected to /login. It's perfectly fine with GET requests of course.


It's worth to mention that actual browser interactions are fine. So it works in dev, but not in test environment.


Anybody else seen this?


XNA project unit testing, builds but errors running tests
Programming Languages

I'm trying to set up some unit tests for an XNA project. After some ordeals with making sure the test project was set to build in the configuration manager and removing references to the XNA content project, I finally got the tests to build.


But the tests still won't run half of the time. If I click "run selection" from the test view I continually get the error "No such interface supported (Exception from HRESULT:0x80004002 (E_NOINTERFACE))." If I instead press the "run all tests in solution" button, it sometimes runs, but usually it gives me this error: "Specific Cast is not Valid." if run all tests does work the first time (this seems to happen after updating from SV


Privacy Policy - Copyrights Notice - Feedback - Report Violation - RSS 2017 © bighow.org All Rights Reserved .