similar to: REPOST: Musings on Rails and logging philosophies

As a perpetual Rails dabbler, I make an awful lot of typical beginner mistakes. And the logs are always either too verbose or too sparse to help me. And it started me thinking. I came from one of the largest production OLTP systems in the world, and the one thing that helped us manage troubleshooting in both development and production was extensive, obsessive, flexible logging. Every operation

Hi all ! I just started writing specs on a new project. I would just like to validate that this is the way you would write it. I know about mocks, stubs and expectations. I don''t think this is a problem for me. My question really boils down to: def index @projects = current_user.projects.active end My spec needs to return the proxy, no ? Here''s my code: context "A

I''ve posted a lengthy description of an authorization plugin for Rails on my blog: http://www.billkatz.com/authorization It describes a proposed DSL for authorization, a pattern for use that describes conventions, and a reference implementation that lets you test the some of the ideas. I hope that some subset of Rails programmers gravitate toward a common DSL for authorization, which

I''ve got a spec that loads a fixture in the "before" block. This works fine running scripts/spec, but when I run rake spec instead, I get: ActiveRecord::StatementInvalid in ''User in fixture :quentin with an IM service but no IM name should be invalid'' Mysql::Error: Cannot delete or update a parent row: a foreign key constraint fails

Using 1.0.8, I just realized that I''ve been scrolling through pages of backtraces when rspec is supposed to clean them up for me. This is a new development machine, so I''m not sure if older versions worked or not. I''m running Ruby 1.8.6, Rails edge, Mac OS X 10.4.10. I''ve verified that the QuietBacktraceTweaker is the one that''s running.

I started using the new Model.should_have(1).records expectation in rspec_on_rails, and quickly realized that my fixtures were remaining loaded, even in contexts that didn''t use them. Bug or feature? Jay Levitt

When I click an InPlaceEditor field in Firefox 1.0.7, the page scrolls up to the top. That''s disconcerting, and often ends up with the editable field out of the viewable pane. I can duplicate this on both Mac and PC. Is there a way to prevent this? Even the demo at http://wiki.script.aculo.us/scriptaculous/show/Ajax.InPlaceEditor does this. Jay Levitt

Just released a new version of the _Managed Fixtures_ plugin, previously known as _Export Fixtures_. The name change comes with some added functionality for managing the fixtures, primarily with two new import tasks for importing specific Models or all of them within the test/fixtures directory. Both new import tasks take the exported fixtures, and allow you to directly import one, or all of

It''s not a critical bug by any means, but shouldn''t InPlaceEditor put DIV tags around the INPUT field? From what I can tell on the W3C validator, INPUT has to be in a block-level tag for XHTML. Of course, there are probably a zillion other things that wouldn''t validate, but every little step helps... Corollary question: Anyone know how to see what contexts a tag

Every once in a while, I pipe up and whine that "belongs_to" should really be ''refers_to" [http://dev.rubyonrails.org/ticket/2130]. It''s time again. I''ve got a bunch of stuff going onto eBay, so, like any good engineer, I don''t just post it manually: I design a Rails-based inventory database that creates a semantically-correct XHTML/CSS auction

Has anyone else run into a problem with trying to use mock_model in spec/lib ? For some reason, I can take the same spec, put it in spec/models, have it run fine, but put it in spec/lib, and have it complain about not being able to find #mock_model Thanks, Edward

I can understand that it''s easier for rspec to set up a mock in advance of the controller call. But it makes it difficult to do something like: context "The HarkController, given Louie the logged-in user" do setup do post :login, :username => ''louie'', :password => ''atest'' end specify "should redirect Louie to the home

TDD, SVN and migrations seem to be a natural combination for model development: create a test, add the column with a migration, write the code, and check it all in when you''re done. The trouble is that this ends up creating one migration per field. I guess it''s not horrible in and of itself, but it does have a code smell to it. Has anyone come up with a different way of doing

When developing applications, Webrick will automatically reload controllers, models, etc. if the source changes. For obvious reasons, it doesn''t do this for plugins, which makes it a pain to develop said plugins. I was hoping Mongrel might have some facility to say "watch this directory too and reload any changes". Obviously, re-init''ing all plugins would be

hey everyone. i know somebody else had started a thread on this subject, but since no one seems to be answering that thread i thought i would start one of my one. i''m doing a project for a client and we need some seriously verbose logging. it looks like log4r can do what i need, but i can''t for the life of me figure out how to plug it into rails. everywhere talks about how

I am getting: undefined method `mock_model'' for [RSpec example]:#<Class:0x25550a8> with my view specs after upgrading to 1.0.8. Is anyone else seeing this? To isolate the message I did the following setup: - create new rails project (with edge) - installed rspec and rspec_on_rails - ran rake spec - ran script/generate rspec_scaffold products - tried to run a builtin view

Hey there folks. I would really like to use log4r as my default logger in Rails, but I''m having a hard time getting it to work. I''m not even sure I''m plugging it in in the right place. I''m using log4r 1.0.5 and rails 1.1.1. I would love it if someone could either point me to a good tutorial on how to use log4r with rails, or at least point me in the right

I''ve been working on a Rails project with one other developer; he was using Test::Unit, and I was using RSpec. That works OK for a while, but obviously it starts causing pain when you have to check in two places to see if a piece of code is properly tested/spec''d, you can''t use TextMate shortcuts to switch back and forth between code and test, you have to duplicate

I know that a given search index doesn't get built the first time until you do an actual search on it from an IMAP client. I don't much care about that; I'm the only user, and I don't create new folders too often. At worst, I could create a script to go search every folder once. But what I'm not clear about: Does it then get updated on every delivery by LDA? Or does the

I have a problem init''ing log4r. I have the following initialization code for log4r: Configurator[''logpath''] = ''./config'' # was ''./logs'' Configurator.load_xml_file(''config/log4r_config.xml'') I put it in appliction.rb, but then ofcourse at every request the logger system will be reinitialized. This causes the