Tests all error after upgrading to 6.5 beta

[Chris Nelson]

I have an existing Rails project where tests pass fine on the command
line, but from inside NetBeans they all fail with an error in
create_fixtures, even though this test doesn't use any fixtures at
all. I was developing this project and running test cases just find
in NB 6.1. Here is a sample stack trace:

4) Error:
test_select_date_with_invalid_date(RecordForeignReprescribeControllerTest):
ArgumentError: interning empty string
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:251:in
`to_sym'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:251:in
`create_fixtures'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:250:in
`map'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:250:in
`create_fixtures'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/base.rb:867:in
`silence'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:248:in
`create_fixtures'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:593:in
`load_fixtures'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:547:in
`setup_with_fixtures'
/Users/superchris/dev/medwiz/medwiz/delanor/development/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:575:in
`setup'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/test/unit/testcase.rb:77:in
`unlogged_run'
/Users/superchris/dev/medwiz/medwiz/delanor/development/test/functional/../test_helper.rb:72:in
`run'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/test/unit/testsuite.rb:34:in
`run'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/test/unit/testsuite.rb:33:in
`each'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/test/unit/testsuite.rb:33:in
`run'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:46:in
`run_suite'

[Erno Mononen]

Hi Chris,

Chris Nelson wrote:

[Chris Nelson]

I tried running them using Test File and Run Focused Test (not from
rake). I'll try with the latest build as well.

--Chris

On Fri, Oct 10, 2008 at 3:36 AM, Erno Mononen <address-removed> wrote:

[Erno Mononen]

OK, let us know whether that helped. If the problem persists, could you
try running 'rake test' both from the IDE and command line (with the
same ruby platform of course) and see whether the problem exists only in
the IDE?

I googled a bit and found the following posts on the same problem, might
be of help to you:

http://1000fires.com/wordpress/?p=21
http://www.ruby-forum.com/topic/148651

Erno

Chris Nelson wrote:

[Chris Nelson]

The same tests run fine under command line and from emacs, so it
something specific to the way NetBeans is running them it appears.
I'll let you know if the new build helps.

On Fri, Oct 10, 2008 at 11:44 AM, Erno Mononen <address-removed> wrote:

[Chris Nelson]

I have the same problem on the new builds. I was finally able to
narrow down what the problem is, and hack in a fix, but don't know
*why* it happened. It appears to be some freaky combination of my
particular project and NB. The issue is that a nil gets passed down
into the Fixtures.create_fixtures method for the table_names param,
but only when I run them in NB. When I run on command line it gets
[]. I fixed by hacking Fixtures to check for nil and set it to [].
But I have no idea how this param gets different values based on
whether I run from NB or not. Also, when created a clean project with
a simple AR test it didn't exhibit this behaviour, so I guess it is
some weird interaction between NB and my specific project.

--Chris

On Fri, Oct 10, 2008 at 11:59 AM, Chris Nelson
<address-removed> wrote:

[Chris Kutler]

A couple of observations

- I know that I don't need to ask this, but when you run from the command line, are you running with the same interpreter/platform that your project is set to?

- Do you know about setting the properties in your config file to get finer log output for Ruby projects so that you can see the actual command the IDE is sending to the the command line? Maybe if you compare that to what you are sending to the command line, you might notice something. It might even be some environment variable setting. See http://wiki.netbeans.org/FaqRubyNBLogging

Chris Nelson wrote:

[Chris Nelson]

On Fri, Oct 10, 2008 at 8:20 PM, Chris Kutler <address-removed> wrote:

[Fjan]

Hi, I had the same problem. I think there are a few methods getting added
somewhere that trip things up. In my case, the start method got overwritten
by Netbeans, and this is what fixed it for me:

class Slot < ActiveRecord::Base
def start;self[:start];end
end

I'm not at all sure if this is something particular to my situation though.


Chris Nelson-5 wrote:

[Erno Mononen]

Hi,

That's interesting info, thanks for sharing it. I would like to track
down the root cause of this, it would be much appreciated if either of
you or anyone else could provide a sample project where this is
reproducible. It might boil down to differences between the console test
runner and the test runner that the IDE uses.

Thanks,
Erno

Fjan wrote:

[Chris Kutler]

I wonder if looking at the local history would help in finding out when
the code got overwritten. Right-click on the file and choose Local
History. Just a crazy idea.

Erno Mononen wrote:

[Fjan]

I tried to reproduce it after downloading the latest nightly and the problem
no longer appears. Something or someone must have fixed it.

Oh well,
Jan


Chris Kutler wrote:

[Erno Mononen]

OK, good to hear it's fixed for you -- there has been a bunch of fixes
in the test runner since Beta. In general I think it is safe to say that
the latest 6.5 builds are preferable over 6.5 Beta (a lot of issues have
been fixed in all areas).

Erno


Fjan wrote:

[bkocik]

I found this thread because I was having the same problem myself. I upgraded
to last night's nightly build of 6.5 (200810170201), and I still have the
issue. The good news is I can easily recreate it for you.

If you happen to have Rails 1.2.6 (or, presumably, any 1.2.x version, though
I only know I can reproduce with 1.2.6 for sure - it doesn't fail with my
2.1.0 projects), try these commands:

rails _1.2.6_ test_fail
cd test_fail
script/generate controller main index

Now open that as a new project in NetBeans, create your test_fail_test
database, and try to run the main_controller_test.rb file. If the stars are
aligned, you'll get a stack trace that begins thusly:

1) Error:
test_truth(MainControllerTest):
ArgumentError: interning empty string

Alternatively, I've created a project using the above steps and have frozen
Rails 1.2.6 into it. You can pick it up here:
http://bkocik.net/tmp/test_fail.tar.gz

I tried to make it work without a DB, but was unsuccessful, so you'll have
to either modify it to do that or create a test_fail_test database in MySQL.

Hope this helps . . .

--
View this message in context: http://www.nabble.com/Tests-all-error-after-upgrading-to-6.5-beta-tp19911408p20033583.html
Sent from the NetBeans Ruby Users mailing list archive at Nabble.com.

[Erno Mononen]

Thanks a lot! That's really helpful, I will try your steps.

Erno

bkocik wrote: