On Tue, May 27, 2008 at 3:33 PM, marcio <[EMAIL PROTECTED]> wrote:
> hello from here! i'm new in rspec and i have a problem while
> installing rspec 1.1.4 gem:
>
> [EMAIL PROTECTED]:~$ gem install rspec
> Bulk updating Gem source index for: http://gems.rubyforge.org
> ERROR: While executing gem ..
hello from here! i'm new in rspec and i have a problem while
installing rspec 1.1.4 gem:
[EMAIL PROTECTED]:~$ gem install rspec
Bulk updating Gem source index for: http://gems.rubyforge.org
ERROR: While executing gem ... (Errno::EACCES)
Permission denied - /var/lib/gems/1.8/cache/rspec-1.1.4.g
Sean,
This is what I have on a project that is running CC.rb with stories:
desc "Task for cruise Control"
task :cruise do
RAILS_ENV = ENV['RAILS_ENV'] = 'test' # Without this, it will drop
your production database.
CruiseControl::invoke_rake_task 'db:reset_all'
CruiseControl::invoke_rake_tas
Thanks! The problem seems to be that the rake spec task is messing up the exit
code of the story spec, but I still can't see how.
When I run the failing story spec outside of a rake task (ruby stories/all.rb),
I get the correct exit code of 1.
When I run it in rake spec:stories, I get the inco
Pat Maddox wrote:
On Tue, May 27, 2008 at 8:41 AM, Sean Miller <[EMAIL PROTECTED]> wrote:
We've just added rspec stories to our CruiseControl.rb build. When there's a
failing scenario we see the failure in the log output, but it doesn't cause the
CruiseControl build to fail. We've also ju
On Tue, May 27, 2008 at 8:41 AM, Sean Miller <[EMAIL PROTECTED]> wrote:
> We've just added rspec stories to our CruiseControl.rb build. When there's a
> failing scenario we see the failure in the log output, but it doesn't cause
> the CruiseControl build to fail. We've also just upgraded to the
We've just added rspec stories to our CruiseControl.rb build. When there's a
failing scenario we see the failure in the log output, but it doesn't cause the
CruiseControl build to fail. We've also just upgraded to the latest rspec
version, 1.1.4, which fixes rspec bug 228, but the CC.rb build
On May 27, 2008, at 9:35 AM, Rick DeNatale wrote:
On Tue, May 27, 2008 at 8:46 AM, David Chelimsky
<[EMAIL PROTECTED]> wrote:
On May 26, 2008, at 7:22 PM, Tim Glen wrote:
So I find myself wondering - is this the case for just helper
modules or
all modules? For instance, I have a module wh
On Tue, May 27, 2008 at 8:46 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> On May 26, 2008, at 7:22 PM, Tim Glen wrote:
>
So I find myself wondering - is this the case for just helper modules or
all modules? For instance, I have a module which gets included into some
controllers
On 27 May 2008, at 15:15, Avdi Grimm wrote:
RCS?
Yes! Something else I've never had the pleasure of using.
I doubt any rspec users use RCS, but you never know.
Ashley
--
http://www.patchspace.co.uk/
http://aviewfromafar.net/
___
rspec-users
On May 27, 2008, at 8:04 AM, Michael Schuerig wrote:
I'd like to finally get started with RSpec, however, not on a complete
(rails or whatever) application, but only on a single rails plugin. In
particular, I want to test the plugin without the context of a
specific
rails app. The only part
On Tue, May 27, 2008 at 10:12 AM, Ashley Moran
<[EMAIL PROTECTED]> wrote:
> Ignore me, I was just being stupid :) I don't really put commas at the end
> of my filenames. I'm sure I've seen something that does though, but I can't
> remember what.
RCS?
--
Avdi
Home: http://avdi.org
Developer Bl
On 27 May 2008, at 14:06, David Chelimsky wrote:
I was thinking more of ant patternsets (from my java days). I think
they support comma or space separated, but all the examples I ever
saw (or wrote) used commas.
Ah ok, I guess it depends on your heritage. I'm lucky to have not had
to bu
On May 27, 2008, at 7:59 AM, Ashley Moran wrote:
On 27 May 2008, at 13:45, David Chelimsky wrote:
How would you do it?
Everywhere I've seen something similar, it's just been space-
delimited, no punctuation.For example, this from the rsync man
page:
rsync -av host:'dir1/file1 dir2
On 27 May 2008, at 13:45, David Chelimsky wrote:
How would you do it?
Everywhere I've seen something similar, it's just been space-
delimited, no punctuation.For example, this from the rsync man page:
rsync -av host:'dir1/file1 dir2/file2' /dest
Not quite the same thing but it's the
On May 26, 2008, at 7:22 PM, Tim Glen wrote:
So I find myself wondering - is this the case for just helper
modules or all modules? For instance, I have a module which gets
included into some controllers, but I'd like to spec against it
directly so I don't have in those other controllers...
On May 27, 2008, at 7:41 AM, Ashley Moran wrote:
On 27 May 2008, at 12:37, David Chelimsky wrote:
I updated my blog post to reflect this:
http://blog.davidchelimsky.net/articles/2008/01/20/rspec-new-pattern-option
Just out of curiosity, how come multiple patterns are specified
comma-sepa
On 27 May 2008, at 12:37, David Chelimsky wrote:
I updated my blog post to reflect this:
http://blog.davidchelimsky.net/articles/2008/01/20/rspec-new-pattern-option
Just out of curiosity, how come multiple patterns are specified comma-
separated? It means I have to go and rename all the fi
On 27 May 2008, at 12:44, andypearson wrote:
def self.cache_all
feeds = self.find(:all)
for feed in feeds
xml = REXML::Document.new Net::HTTP.get(URI.parse(feed.url))
xml.elements.each '//item' do |item|
Item.prepare_and_save(feed, item)
end
end
end
Problems are now beginning
I'd like to finally get started with RSpec, however, not on a complete
(rails or whatever) application, but only on a single rails plugin. In
particular, I want to test the plugin without the context of a specific
rails app. The only parts of rails that I need are ActiveRecord and
ActiveSuppor
On 27 May 2008, at 12:44, andypearson wrote:
xml = REXML::Document.new Net::HTTP.get(URI.parse(feed.url))
It won't make the problem go away, but you can certainly reduce the
blizzard of intermediate stubs by pulling this chain out into its own
method (e.g. fetch_xml_from_url) and stubbin
Hello all,
In yet another attempt to learn Ruby on Rails and Rspec I have started
writing a simple life streaming app with will aggregate feeds from several
places and save them in a database for later use.
An internet search eventually led me to the following method for looping
through the feed
On May 27, 2008, at 2:35 AM, kasutaja wrote:
Hello.
You're saying that:
To get rspec to behave as it did before this change, use this:
--pattern "**/*.rb"
That was an error. Use this instead:
--pattern "spec/**/*.rb"
or this if you want to avoid loading files other than spec files:
--pat
On May 27, 2008, at 6:06 AM, Rick DeNatale wrote:
On Mon, May 26, 2008 at 5:52 PM, David Chelimsky
<[EMAIL PROTECTED]> wrote:
The RSpec Development Team is happy to announce the release of
RSpec-1.1.4.
See http://rspec.info/changes.html for details of what changed in
this
release.
For R
On Mon, May 26, 2008 at 5:52 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> The RSpec Development Team is happy to announce the release of RSpec-1.1.4.
>
> See http://rspec.info/changes.html for details of what changed in this
> release.
>
> For Rails developers:
>
> * This release of RSpec suppo
On 27.5.2008, at 10.52, Mark Dodwell wrote:
Also, any opinions on using a Factory pattern for instantiating
mocks of
models? I like the idea of maintaining mocks in one place as I
frequently use them across several specs for models that have
associations. Do you think it would create dependen
Also, any opinions on using a Factory pattern for instantiating mocks of
models? I like the idea of maintaining mocks in one place as I
frequently use them across several specs for models that have
associations. Do you think it would create dependency issues between the
specs using that Factory
Many thanks for your replies.
David Chelimsky wrote:
> Use stub_model instead (if you're using source from github - if not
> the 1.4 release is coming soon).
Thanks - that helps a great deal.
Scott Taylor wrote:
> I would highly suggest using :null_object => true in view specs (or
> controller
Hello.
You're saying that:
To get rspec to behave as it did before this change, use this:
--pattern "**/*.rb"
I tried like this (rspec 1.03) and it wasn't same as before (rspec 1.08).
Now it also loads all other files in current directory and in all
subdirectories and not only from directory
On 26-mei-2008, at 21:52, Mark Dodwell wrote:
I find myself doing this kind of thing a lot in Controller Specs:
@vacancy = mock_model(Vacancy)
@vacancy.stub!(:reference)
@vacancy.stub!(:title)
@vacancy.stub!(:created_at)
@vacancy.stub!(:updated_at)
@vacancy.
On 27 May 2008, at 01:22, Tim Glen wrote:
whiz_banger = Object.new
whiz_banger.extend WhizBangModule
I like that as far as it goes, but I'm wondering if there's a way to
take it one step further and actually have it extend the typical
controller functionality - some of my methods make use
31 matches
Mail list logo
