gmane.comp.java.netbeans.modules.ruby.devel

Re: Test runner question about clicking on nodes of failed classes

Chris Kutler — 2008-08-29T17:23:34

Hi Erno, I don't think I am understanding what you mean by first line in stack trace. I have attached two images, one for RSpec tests and one for Unit Tests. In the one for RSpec, double-clicking the test takes me to the second line in the trace. In the one for unit tests, double-clicking takes me to the test and not any line in the trace, that I can see. I will be sending you this app in response to another email, so maybe you can see what I mean. Erno Mononen wrote: --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe-n3CzLFQkLgrXWKka9uoeGti2O/JbrIOy< at >public.gmane.org For additional commands, e-mail: dev-help-n3CzLFQkLgrXWKka9uoeGti2O/JbrIOy< at >public.gmane.org

Re: Trying to understanding rules when project has both unit tests and rspec tests

Chris Kutler — 2008-08-29T16:08:51

Great! thanks. Martin Krauskopf wrote:

Re: Need advice for user problem with Generator UI picking up 1.2.6 even though 2.1.0 is installed

Erno Mononen — 2008-08-29T08:25:04

Hi Chris, Chris Kutler wrote: I think not, but shouldn't be too hard to fix that. Could you please file an issue for this? Erno

Re: Understanding Step Over in Rails Debugging, seems like funny things happening

Martin Krauskopf — 2008-08-29T08:15:53

The stepping is driven by debugger backend. Please file a bug against ruby/debugger with details (platform, server) and ideally step to reproduce if possible. I've been debugging MRI/Mongrel few hours yesterday without problems. Also quickly tried your case now without being able to reproduce. Thanks, m.

Re: Test runner question about clicking on nodes of failed classes

Erno Mononen — 2008-08-29T07:53:31

Hi Chris, Chris Kutler wrote: What's the first line in the stack trace in this case? Double clicking a failed node jumps to the location specified by the first line in the stack trace (for better or worse). Erno

Re: Trying to understanding rules when project has both unit tests and rspec tests

Martin Krauskopf — 2008-08-29T07:46:21

Fixed: #c1ef9cda3b00 Will be likely available since build 3614 or later. m.

Re: Trying to understanding rules when project has both unit tests and rspec tests

Martin Krauskopf — 2008-08-29T07:03:33

[...] [...] The underlaying code behaves like that. Seemingly bug, I'll fix it to prefer the test in all cases when both, rspec and test, are available. Thanks for the catch, m.

Test runner question about clicking on nodes of failed classes

Chris Kutler — 2008-08-29T03:13:48

In the test runner (Test Results tab), double-clicking on a node does different things depending on whether it is a unit test or an RSpec test. - double-clicking a node for a failed unit test takes me to that test method - double-clicking a node for a failed RSpec test (a specify or it block) takes me to the line in the class being tested that caused the failure. Is this the way it is supposed to be?

Understanding Step Over in Rails Debugging, seems like funny things happening

Chris Kutler — 2008-08-29T03:06:20

Here is what I believe the definition of Step Over is: Step Over. Executes one source line of a program. If the line is a method call, executes the entire method then stops. Often times, when debugging a test, Step Over (in the actual controller class) takes me into the method call. For example, it stops at this breakpointed line < at >calendar = Calendar.find(params[:id]) I click Step Over and it stops at the following line in filters.rb if controller.send!(:performed?) Step Out takes me to this line in filters.rb def call(controller, &block) Is that a bug or is there a reason for this. Sometimes when this happens, I try Step Out to get back but I don't seem to be able to. so I click Continue. When I do that, I end up having to click Continue a lot ,with it stopping in a lot of places deep down that didn't have break points. Eventually, I hit some wall and the class simply stops running.

Trying to understanding rules when project has both unit tests and rspec tests

Chris Kutler — 2008-08-29T01:11:26

I am not sure this is a scenario that would really exist (that developers would have both unit tests and rspec tests), but I do and I have some questions. calendars_controller.rb has RSpec > controllers > calendars_controller_spec.rb Functional Tests > calendars_controller-test.rb Pop-up menu Navigate > Go to Tested Class takes me to calendars_controller.rb for both files. Pop-up menu Navigate > Go to Test in calendars_controller.rb takes me to calendars_controller_spec.rb Pop-up menu Test File in calendars_controller.rb runs calendars_controller_spec.rb So, one would think that RSpec files take priority over unit test files. However, with the model tests, the unit test takes priority. Models > calendar.rb has Unit Test > calendar.rb RSpec > models > calendar_spec.rb Go to Tested class for both takes me to calendar.rb Go to Test takes me to calendar_test.rb, not calendar_spec.rb Test File runs the calendar_test class, not the calendar_spec test Why

Re: server output text in red...

Martin Krauskopf — 2008-08-28T18:35:38

Yes, the stderr is red. stdout is normal (black). It depends on the server. Seems that Mongrel is not so stderr-ish as WEBrick. Thus no. m.

server output text in red...

Peter Williams — 2008-08-28T18:15:04

Is there a reason the rails servers show their all text (except links) in red in the output window (most likely due to all their output being channelled through stderr in the output window api, though I haven't checked). Or is this a bug? -Peter

Need advice for user problem with Generator UI picking up 1.2.6 even though 2.1.0 is installed

Chris Kutler — 2008-08-28T15:40:44

Hello, A user wrote to me that when they run the 6.1 Generator and pick Scaffold from the drop-down, they are not seeing the Rails 2.1 prompts of Model Name/Attribute Pairs, but instead Model Name/Controller Name/Actions. In the environment.rb, the statement is as follows: RAILS_GEM_VERSION = '2.1.0' unless defined? RAILS_GEM_VERSION RAILS_GEM_VERSION is not set. This happens when using their MRI Ruby installation (1.8.6-p114) In the Gems manager, the rails version displayed in the Installed tab is 2.1.0, 1.2.6 When they create a new Ruby on Rails Application, step 4 in the Wizard dialog (Install Rails) displays: "Rails appears to be installed." and the Installed version is set to *1.2.6.* If they click on the Update Rails button, the following status appears: Updating installed gems HEAD 200 OK: http://gems.rubyforge.org/latest_specs.4.8 Nothing to update They tried setting RAILS_GEM_VERSION to 2.1.0 but that did not help. Is there a way to get the IDE to display the Rails 2.1 generator

Re: How do I see this GSF UI

Chris Kutler — 2008-08-28T05:02:17

I am not seeing these. Not seeing them under Options > Keymap > Edit Source Ruby Tor Norbye wrote:

Re: Understanding Test Runner output with RSpec files?

Chris Kutler — 2008-08-28T04:57:44

No need to answer this, I am using the 1.1.4 rspec and rspec_rails plugins now and am ok so far. Chris Kutler wrote:

Re: Understanding Test Runner output with RSpec files?

Chris Kutler — 2008-08-28T04:50:29

Ignore my late night mumblings. It wasn't breaking on my lines because my lines were not being executed, as should be. Chris Kutler wrote:

Re: Understanding Test Runner output with RSpec files?

Chris Kutler — 2008-08-28T04:45:02

This bug is also preventing me from debugging my 1.1.4 rspec and rspec_rails plugin spec files. It doesn't even stop at the breakpoint. I can supply a sample app if you want. Ask for RailsApplication3. Chris Kutler wrote:

Re: Understanding Test Runner output with RSpec files?

Martin Krauskopf — 2008-08-27T21:59:02

> I am now getting inconsistent behavior. Sometimes I do see the failure > in the left side. I am trying to figure out how to make it work, and > make it not work. I will show the the spec file in the next email. > > In the meantime, I just got this when I chose Run from my spec file. I > can send the log directly to you if you want. > > java.lang.AssertionError > at org.netbeans.modules.ruby.testrunner.ui.TestsuiteNode.(TestsuiteNode.java:93) > at org.netbeans.modules.ruby.testrunner.ui.TestsuiteNode.(TestsuiteNode.java:75) [...] This seems to be another case of 'random' issue: http://www.netbeans.org/nonav/issues/show_bug.cgi?id=145228 You might CC you self there to watch the progress. Actually the issue is about ISE, but I was told this is related to AE. I'm increasing to P2, since it seems to be frequently encountered one. m.

Re: Understanding Test Runner output with RSpec files?

Chris Kutler — 2008-08-27T19:28:14

OK, here are variations of my test file that have expected output and unexpected output. Please don't laugh too hard at my spec files. I am just learning how to do RSpec files and I am obviously clueless (but sometimes clueless people are good at exposing bugs because we do the unexpected :-P ) This is the spec file that that shows No tests executed/Item passed. ===================================== require 'item' describe Item do PRICE = 24.95 TYPE = "book" ID = 1 it "should have the specified id type and price " do item = Item.new(ID, TYPE, PRICE) item.price should == PRICE item.id should == ID item.type should == TYPE end end ==================================== Here is one that has expected results. That is, I see No test passed, 1 test failed - (icon) Item Failed + (icon) should have bla bla bla If you happen to know what I should be doing to test the values, please let me know. My failure message is 'Item should have the specified id type and price ' FAILED

Re: Understanding Test Runner output with RSpec files?

Chris Kutler — 2008-08-27T19:06:44

I am now getting inconsistent behavior. Sometimes I do see the failure in the left side. I am trying to figure out how to make it work, and make it not work. I will show the the spec file in the next email. In the meantime, I just got this when I chose Run from my spec file. I can send the log directly to you if you want. java.lang.AssertionError at org.netbeans.modules.ruby.testrunner.ui.TestsuiteNode.(TestsuiteNode.java:93) at org.netbeans.modules.ruby.testrunner.ui.TestsuiteNode.(TestsuiteNode.java:75) at org.netbeans.modules.ruby.testrunner.ui.RootNodeChildren.createNode(RootNodeChildren.java:278) at org.netbeans.modules.ruby.testrunner.ui.RootNodeChildren.displayReport(RootNodeChildren.java:144) at org.netbeans.modules.ruby.testrunner.ui.RootNode.displayReport(RootNode.java:147) at org.netbeans.modules.ruby.testrunner.ui.ResultPanelTree.displayReport(ResultPanelTree.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.ref

Re: Understanding Test Runner output with RSpec files?

Erno Mononen — 2008-08-27T18:42:16

Hi Chris, I'd need to see the spec file to be able to answer, could you please post it here (or to me) or file an issue for this? Sounds like it could be a bug, but hard to say for sure without seeing the file. Thanks, Erno Chris Kutler wrote: