search for: wilden

-- Sent from my mobile device

I know there is a hash_including, which is quite useful. Are there by chance any matchers for ensuring a hash includes only the specified values, or that it doesn''t have certain values? Thanks, Steve

I expected ''should !='' to act the same as ''should_not ==''. That turned out to be incorrect (by design?): require ''spec'' require ''spec/rails'' describe "using ''should !=''" do it "seems to treat != as the same as ==" do 1.should != 1 # passes 1.should != 2 # fails end end

In tracking down a bug in AuthLogic I realized that I had made the same error in one of my libraries. Knowing what the error was made creating a test to expose it (using cucumber) rather trivial. However, it has occurred to me that this sort of issue is far more subtle than I first appreciated. So, I am looking for some opinions on how to test for this sort of thing in a more general sense. At

How can I link to a CSS file in one of my view files? -- Posted via http://www.ruby-forum.com/.

I''m trying to decide which IDE to go with for RoR development. I put a high premium on integrated test automated tools and debugging capabilities. I''d appreciate any sharing of experience. I''m currently running Instant Rails on a Windows 2000 box (using IR due to problems I encountered trying to get all the components set up individually). Also, I''m using

Hey Guys. I just updated a project form 1.1.4 that was working with autotest 3.10 without issues: 1) Updated spec/model/project_spec.rb and it fired only that spec. 2) Updated app/model/project.rb and it fired only the matching spec file. After the update of rspec and rspec-rails as plugins a few minutes ago, it only run the controller specs and no other. Also, it doesn''t matter which

Here is a very simple spec: -- require File.expand_path(File.dirname(__FILE__) + ''/../spec_helper'') describe Product, "The Product model" do describe "When a new blank product object gets created" do before(:each) do @product = Product.new end it "should not be valid" do @product.should_not be_valid

...treams out of a FIFO, and apart from the fact that the backend programming sometimes makes shout crash for that, other than that it plays fine. thomas <-*- -*-> Ik zei dat ik voor haar wou sterven en dat vond zij niet fijn Zij hield van dieren en van mensen die in leven wilden zijn <-*- thomas@apestaart.org -*-> URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/ --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@...

en.com On: Wed Nov 12 12:46:54 EST 2008, Mark Wilden mark at mwild wrote: > On Wed, Nov 12, 2008 at 9:27 AM, James B. Byrne <byrnejb at harte- > lyne.ca> wrote: > >> Feature: Manage entities # features/manage_entities.feature >> > > This is just a side note, but is "manage entities" really a feature? It &...

A controller I''m trying to test simply delivers a text string to the client, which then demarshalls it to retrieve some objects. I want to test that the returned string is correct. I don''t want to compare the string character-by-character with response.has_text because that ties me to the implementation of the Marshall class. Instead, I just want to demarshall the string

Hi all, I have what I thought was quite a simple requirement but something to do with the way ActiveRecord''s associations work is making it quite puzzling. I guess I can sum it up with this failing test: before(:each) do @source_comment = @source.comments.create(:user_id => 1) @target_comment = @target.comments.create(:user_id => 1) end

The following statement gave me "wrong number of arguments (2 for 1)" and it is the only error. no stack trace. presenter.stub!(:account).and_return account any idea? Thanks Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090225/8e667eea/attachment.html>

I was disgruntled with the amount of spam I was getting, so I started setting up accounts for the various mailing lists I listen to. I use rspec at showcase60.com to read the mail here. Along with the rspec news that comes over this channel, I''m getting more and more spam addressed to this same account, which means that the open way this list passes around email addresses is

I''ve broken away -- partially at least -- from the dark side. I''m a long-time MS dev. I heard about Ruby and RR from Scott Hanselman (http://www.hanselman.com/blog/). He''s a great blogger on things in the MS world but he''s always provided a broader perspective. And he found great beauty in Ruby and RR and said as much. I had the opportunity to try out

Just wanted to let everyone know that I just posted an updated CHM file that contains documentation for Rails Version 1.0. You can read all about it here<http://www.delynnberry.com/articles/2006/02/07/rails-chm-documentation-version-1-0>. I plan to continue updating the CHM file as newer versions of Rails are announced, but I also want to finish an article that includes a rake file that will

Greetings, How to write Example which will check if model''s variable''s format is valid using :on => :create, like this: class User < ActiveRecord::Base ... validates_format_of :email, :with => /.../, :on => :create ... Using following code is not right: it "should ..." do @user = users(:example_user) @user.email =

Hi, does anybody set up an icecast server delivering streams > 160KBit/s ? I tried that with liveice and shout but in both cases the stream stutters very much. So, I have eliminated the Net (stream to localhost), the CPU (P3/800 should be fast enough), and lame (can encode 320kBit/s 3 times faster then the wav has secs). So the Problem should be icecast. can anybody please enlight me?

Now that we have the big Rails 2.0 release out the door, it''s a lot easier to push out smaller updates more frequently. So that''s what we''re going to do. Rails 2.0.2 contains a bunch of smaller fixes to various bugs, no show-stopping action, just further polish. But it also contains a few new defaults:

anyone able to explain logic behind "rake spec" startup? i.e. the below steps & why things occur when they do Macintosh-2:myequity greg$ rake spec --trace (in /Users/greg/source/myequity) ** Invoke spec (first_time) ** Invoke db:test:prepare (first_time) ** Invoke db:abort_if_pending_migrations (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute