On Mon, 22 Sep 2008 21:57:20 -0400, Scott Taylor
[EMAIL PROTECTED] said:
On Sep 22, 2008, at 8:11 PM, Bryan Helmkamp wrote:
At my job, our story suite contains over 500 scenarios. While we're
very happy with the regressions we've caught by running the suite, the
long time it takes (~
On 23 Sep 2008, at 02:35, David Chelimsky wrote:
This should work right now with both 'rake spec' and 'cucumber
features'
It does, but only as cucumber features if I do cucumber features/
descriptions/xyz.feature it doesn't find the the step file on it's own.
Ben's TextMate Cucumber
I came up with this code:
def mock_result(stubs = {})
@result ||= mock('Object', stubs)
end
describe being an administrator do
it should create a new user using OpenID authentication do
@controller.should_receive(:authenticate_with_open_id).with(@identity_url,
On Tue, Sep 23, 2008 at 2:07 PM, Brandon Keepers [EMAIL PROTECTED] wrote:
On Mon, Sep 22, 2008 at 9:52 AM, David Chelimsky [EMAIL PROTECTED]
wrote:
Hey all,
Let's make this official. We're planning to replace the RSpec Story
Runner with Cucumber. The rspec-1.1.5 release will still include
On Tue, Sep 23, 2008 at 5:21 AM, Ashley Moran [EMAIL PROTECTED]
wrote:
This is just how I use it anyway - maybe I'm alone in adding extra folders
like that. But I still find the nested structure much more logical than the
partially flat one.
I agree. I tried nesting too without any luck.
On Tue, Sep 23, 2008 at 4:21 AM, Ashley Moran
[EMAIL PROTECTED] wrote:
On 23 Sep 2008, at 02:35, David Chelimsky wrote:
This should work right now with both 'rake spec' and 'cucumber features'
It does, but only as cucumber features if I do cucumber
features/descriptions/xyz.feature it
I have one question outside of rspec land in regards to cucumber.
I've used it with test unit, test spec, and rspec without issue.
Will it still be a relatively easy require to use on projects outside
of rspec? More specifically, is the plan to have it replace story
runner within rspec, or to
On Tue, Sep 23, 2008 at 7:53 AM, Chad Humphries
[EMAIL PROTECTED] wrote:
I have one question outside of rspec land in regards to cucumber.
I've used it with test unit, test spec, and rspec without issue.
Will it still be a relatively easy require to use on projects outside
of rspec? More
I would like to use rspec to test a model that leverages acts_as_solr.
I think I want to render rebuild_solr_index and solr_commit and
perhaps other methods that call out to the Solr server moot by having
those functions simply return true. (I will build other tests to make
sure my Solr
So we've got a pretty decent number of specs now, and despite my best
efforts, AR is just forcing us down the path of having to use
database interaction for some of the model specs.
It's starting to get tiring to run all the specs now, which is making
me sad, and making me worry about how
Matt Wynne wrote:
So we've got a pretty decent number of specs now, and despite my best
efforts, AR is just forcing us down the path of having to use database
interaction for some of the model specs.
Just out of curiosity, I would be interested to know how AR is forcing
you to use database
Martin Streicher [EMAIL PROTECTED] writes:
I would like to use rspec to test a model that leverages
acts_as_solr. I think I want to render rebuild_solr_index and
solr_commit and perhaps other methods that call out to the Solr
server moot by having those functions simply return true. (I will
Hi,
I am currently moving over my Watir Story Runner tests over to Cucumber.
However, I have a verification_steps.rb that holds these two steps
Then the user is at '$title' page do |title|
browser.wait_until_includes(title)
end
Given the user is at '$title' page do |title|
On Tue, Sep 23, 2008 at 6:18 PM, aidy lewis [EMAIL PROTECTED] wrote:
Hi,
I am currently moving over my Watir Story Runner tests over to Cucumber.
However, I have a verification_steps.rb that holds these two steps
Then the user is at '$title' page do |title|
On Tue, Sep 23, 2008 at 3:39 AM, CarmineM [EMAIL PROTECTED] wrote:
I came up with this code:
def mock_result(stubs = {})
@result ||= mock('Object', stubs)
end
describe being an administrator do
it should create a new user using OpenID authentication do
Mark, if by any chance you should ever be in Italy (near by Naples),
please drop me a line
I owe you a lot more than a beer, but that would do for a start :).
Thanks so much for every word and every second spent in helping me!
I had to write tests after some code has been written, because I'm
On Tue, Sep 23, 2008 at 10:27 AM, CarmineM [EMAIL PROTECTED] wrote:
Mark, if by any chance you should ever be in Italy (near by Naples),
please drop me a line
Ooo, that's a deal! My son's in his third year of Italian, and I just made
my first ragu Bolognese. :)
///ark
Hi,
I updated my rspec and rspec-rails plugins from 1.1.3 to 1.1.4
Doing script/generate rspec, seemed to have worked, but now when I want
to run rake spec, I get the following error message:
--
/usr/local/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no
Argh, installing rspec in a fresh new rails app worked. I guess
something got borked in the upgrade process.
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
I found where the bug was coming from:
I initialize my plugins using:
For my default config:
config.plugins = [ :some_plugin ]
For my development environment:
config.plugins = [ :all ]
For some strange reason, rspec doesn't like this statement, so when I
remove them all, the it now works.
--
Is it normal behavior that when a test fails, I get an error message at
the end such as:
---
rake aborted!
Command /usr/local/ruby/bin/ruby -I...
---
When all the tests pass, I don't get any error message though. But
having this error message when a test fails makes me feel that there was
an
I have one last problem. Now autotest only executes tests that sit in
test/ folder, and doesn't seem to run the specs.
How do I correct that?
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
On 23 Sep 2008, at 16:25, Joseph Wilk wrote:
Matt Wynne wrote:
So we've got a pretty decent number of specs now, and despite my
best efforts, AR is just forcing us down the path of having to use
database interaction for some of the model specs.
Just out of curiosity, I would be interested
On 23 Sep 2008, at 16:49, Pat Maddox wrote:
Matt Wynne [EMAIL PROTECTED] writes:
So we've got a pretty decent number of specs now, and despite my
best efforts,
AR is just forcing us down the path of having to use database
interaction for
some of the model specs.
Why don't you put the
that's actually good - mine is broken an will only run specs.
use script/autospec to run specs.
now you can run both at once!
On 23 Sep 2008, at 23:03, Fernando Perez wrote:
I have one last problem. Now autotest only executes tests that sit in
test/ folder, and doesn't seem to run the specs.
On Sep 23, 2008, at 11:49 AM, Pat Maddox wrote:
Matt Wynne [EMAIL PROTECTED] writes:
So we've got a pretty decent number of specs now, and despite my
best efforts,
AR is just forcing us down the path of having to use database
interaction for
some of the model specs.
It's starting to get
On Mon, Sep 22, 2008 at 9:57 PM, Scott Taylor
[EMAIL PROTECTED] wrote:
Let me know if you come up with something - I'd be interested in
contributing to such a project.
I started working on a project I'm calling Testjour to solve this at
http://github.com/brynary/testjour/tree/master .
It's not
27 matches
Mail list logo