I just wanted to confirm that you've verified that the exact same
codebase has its specs run correctly on a different OS (or flavour of
linux, even)?
Best,
Sidu.
http://c42.in
http://about.me/ponnappa
On 29 March 2011 06:34, Carlos Torres wrote:
> I'm new to Rails and I was planning on trying
On Mar 28, 2011, at 3:53 PM, snelson wrote:
> I have a commit to add support for the -p (parallel) option to
> autotest, which is a feature provided by @grosser's autotest fork.
>
> The discussion is here: https://github.com/grosser/autotest/issues/#issue/13
> The commit is here:
> https://githu
On 28 Mar 2011, at 04:04, Mike T wrote:
> Any ideas? All I'd like to do is have two specs in different files use the
> same shared example group. I saw a similar thread about autotest, but I am
> not using that.
>
> $ uname -a
> Darwin mbp.local 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10
I use VCR to record interactions, and when the recordings change
filenames, and directory structure, over time, as the test suite
evolves, the old recordings, no longer used, are rarely pruned.
I would like to have the ability to run rspec with an option to check
for unused VCR recordings, and ano
I use VCR to record interactions, and when the recordings change filenames,
and directory structure, over time, as the test suite evolves, the old
recordings, no longer used, are rarely pruned.
I would like to have the ability to run rspec with an option to check for
unused VCR recordings, and ano
Any ideas? All I'd like to do is have two specs in different files use the
same shared example group. I saw a similar thread about autotest, but I am
not using that.
$ uname -a
Darwin mbp.local 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17
PST 2010; root:xnu-1504.9.26~3/RELEASE_I386
Hi,
I'm using Rspec + Capybara in Rails3.
My integration tests went well today until I couldn't even access a
page with simple requests such as:
visit root_path
With error:
Rack application timed out during boot
Any idea of what's going on?
___
I'm new to Rails and I was planning on trying out RSpec. When I try to
execute the rspec command on Debian v6.0.1, I get the output below:
k4ru050@DebianBox:~/Desktop/rails_projects/sample_app/spec$ bundle exec
rspec spec/controllers
/home/k4ru050/.rvm/gems/ruby-1.9.2-p180@rails3tutorial/gems/rspe
Hi there,
Does RSpec acknowledge bundler, and use the groups?
Also is there any good example of what is required for a function spec
rake task...
I've had issues trying to create my own.
require 'rubygems'
require 'bundler'
Bundler.setup(:default, :test)
begin
require 'rspec/core/rake_task'
I'm testing a Rails 3 app with Rspec and Capybara.
For my integration tests, I need to test javascript. Of course, I
watched http://railscasts.com/episodes/257-request-specs-and-capybara
which presents the basics very well.
Unfortunately an error is raised in the javascript as I can see using
sav
I had a similar problem, then I noticed that I didn't include gem
'rspec-rails' in my development environment like what David mentioned
above.
That fixed the problem I had. I'm running the following stack:
- rails 3.0.3
-
- rake (0.8.7)
- rspec 2.5.0
- rspec-rails 2.5.0
On Feb 23, 10
Hello all,
I recently released a gem that assists in testing XML nodes for
equivalency, and thought it might be of interest to the RSpec
community. It can normalize whitespace (or not), ignore element order
(or not), compare namespaces based on URI (not prefix), and more. Plus
-- and possibly best
I have a commit to add support for the -p (parallel) option to
autotest, which is a feature provided by @grosser's autotest fork.
The discussion is here: https://github.com/grosser/autotest/issues/#issue/13
The commit is here:
https://github.com/thisbythem/rspec-core/commit/de074af8ab19e432b3c7b3
Any ideas? All I'd like to do is have two specs in different files use
the same shared example group. I saw a similar thread about autotest,
but I am not using that. [Sorry for the double post on Google Groups;
didn't realize at the time it was a read-only group.]
$ ruby -v
ruby 1.8.7 (2009-06-12
On Apr 2, 2011, at 6:20 AM, Kai Schlamp wrote:
> I use RSpec mock and stub like this:
>
> hit = mock("hit", :stored => 5)
>
> This works fine, but when using this instead:
>
> hit = mock("hit").stub(:stored) { 5 }
Not that it's really necessary, but to make this work you can do:
hit = mock('h
> hit = mock('hit')
> hit.stub(:stored) { 5 }
> hit.stored.should eq(5)
>
> Make sense?
Of course :-) Thanks.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Apr 2, 2011, at 8:20 AM, Kai Schlamp wrote:
> I use RSpec mock and stub like this:
>
> hit = mock("hit", :stored => 5)
>
> This works fine, but when using this instead:
>
> hit = mock("hit").stub(:stored) { 5 }
>
> then I get
>
> undefined method `stored' for # 0xb688bb78>
>
> I always th
I use RSpec mock and stub like this:
hit = mock("hit", :stored => 5)
This works fine, but when using this instead:
hit = mock("hit").stub(:stored) { 5 }
then I get
undefined method `stored' for #
I always thought both were equivalent. Can someone enlighten me?
Regards,
Kai
__
18 matches
Mail list logo