Subject pretty much asks the question
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Jun 5, 2010, at 12:42 PM, Brian Cardarella wrote:
> Subject pretty much asks the question
You _can_, but if you use ActiveRecord and start off with a clean DB, you can
use_transactional_examples (alias for use_transactional_fixtures, which
defaults to true in beta.10, but will default to fal
Using RSpec 2 beta.
$ rspec spec
* spec/spec.opts is deprecated.
* please use .rspec or ~/.rspec instead.
I tried renaming the file to .rspec but then it has no effect!
# spec/.rspec
--format nested
--color
It works if I copy it to ~/.rspec and it turns out, also if I
copy .rspec to the root o
On Jun 5, 2010, at 3:08 PM, Kristian Mandrup wrote:
> Using RSpec 2 beta.
>
> $ rspec spec
>
> * spec/spec.opts is deprecated.
> * please use .rspec or ~/.rspec instead.
>
> I tried renaming the file to .rspec but then it has no effect!
>
> # spec/.rspec
> --format nested
> --color
>
> It wor
David,
I'm not seeing that behavior.
I have beta.10 and without using database_cleaner data is persisting
after each spec and from suite run to suite run. I thought
database_cleaner would resolve the issue but it doesn't seem to.
- Bran
On Jun 5, 2:12 pm, David Chelimsky wrote:
> On Jun 5, 201
Thanks ;)
I also tried to follow the instructions on using autospec/autotest,
first from the RSpec book then from instructions found on the net.
I managed to do the following so far:
# config/cucumber.yml
default: --format profile features
html_report: --format progress --format html --
out=feat
On Jun 5, 2010, at 3:12 PM, David Chelimsky wrote:
> On Jun 5, 2010, at 3:08 PM, Kristian Mandrup wrote:
>
>> Using RSpec 2 beta.
>>
>> $ rspec spec
>>
>> * spec/spec.opts is deprecated.
>> * please use .rspec or ~/.rspec instead.
>>
>> I tried renaming the file to .rspec but then it has no e
On Jun 5, 2010, at 3:34 PM, Brian Cardarella wrote:
> On Jun 5, 2:12 pm, David Chelimsky wrote:
>> On Jun 5, 2010, at 12:42 PM, Brian Cardarella wrote:
>>
>>> Subject pretty much asks the question
>>
>> You _can_, but if you use ActiveRecord and start off with a clean DB, you
>> can use_transa
It seems there is no bin/autospec with RSpec 2. So I got it running
simply with $ autotest
Been looking at instructions here
http://wiki.github.com/dchelimsky/rspec/autotest-integration
And here http://ph7spot.com/musings/getting-started-with-autotest
But...
$ RSPEC=true autotest
loading autot
On Jun 5, 2010, at 3:53 PM, Kristian Mandrup wrote:
> It seems there is no bin/autospec with RSpec 2. So I got it running
> simply with $ autotest
>
> Been looking at instructions here
> http://wiki.github.com/dchelimsky/rspec/autotest-integration
>
> And here http://ph7spot.com/musings/getting
Sorry, forgot to answer the other question. I am using ActiveRecord.
Just a greenfield Rails 3.0.0.beta3 app
- Brian
On Jun 5, 3:42 pm, David Chelimsky wrote:
> On Jun 5, 2010, at 3:34 PM, Brian Cardarella wrote:
>
> > On Jun 5, 2:12 pm, David Chelimsky wrote:
> >> On Jun 5, 2010, at 12:42 PM,
Yeah, I'm not certain what the deal is.
Here is my spec_helper: http://pastie.org/993256
I was using Spork but commented it out to see if that was an issue.
Nope.
I was using sqlite to see if the lack of a real transactional database
was the issue. (changed to postgres) Nope.
Not certain if this
Ok, something else is going on because I just generated a brand new
app with rspec-2.0.beta.10 and the transactions are working just fine.
Sorry about that, I'll track down the issue.
- Brian
On Jun 5, 4:12 pm, Brian Cardarella wrote:
> Sorry, forgot to answer the other question. I am using Acti
On Jun 5, 2010, at 4:11 PM, Brian Cardarella wrote:
> Yeah, I'm not certain what the deal is.
>
> Here is my spec_helper: http://pastie.org/993256
>
> I was using Spork but commented it out to see if that was an issue.
> Nope.
> I was using sqlite to see if the lack of a real transactional datab
Okay, it's going to be one of those weekends. I forgot to wrap the
example in an 'it' block. It was just a bare 'context' block running
the code. False alarm! :D
- Brian
On Jun 5, 4:21 pm, David Chelimsky wrote:
> On Jun 5, 2010, at 4:11 PM, Brian Cardarella wrote:
>
> > Yeah, I'm not certain wh
On Jun 5, 2010, at 4:20 PM, Brian Cardarella wrote:
> Ok, something else is going on because I just generated a brand new
> app with rspec-2.0.beta.10 and the transactions are working just fine.
> Sorry about that, I'll track down the issue.
Happens :)
Good luck.
>
> - Brian
>
> On Jun 5, 4:1
Thanks again David :)
> Don't use RSPEC=true for rspec-2.
>
> Also, probably need to set AUTOFEATURE=false.
>
OK, when I run it like this
$ AUTOFEATURE=false autotest
I get an empty autotest output whenever I change and save a spec.
The above lets me disable features, but how do I ENABLE specs
I found the solution here: http://blog.davidchelimsky.net/category/autotest/
--
As of beta.4, you’ll have to do add this configuration manually. Just
create an autotest directory in the root of your project, put the
following statement in ./autotest/discover.rb:
Autotest.add_discovery { "rspec2"
Thanks! I solved it all now and updated the RSpec 2 wiki about how to
set it all up ;)
http://wiki.github.com/rspec/rspec/autotest
Hope these instructions provides a good base and is helpful to others!
___
rspec-users mailing list
rspec-users@rubyforge.
19 matches
Mail list logo