I added basic information to the README: https://github.com/rspec/rspec-core
--
David Chelimsky
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Saturday, April 7, 2012 at 9:59 AM, David Chelimsky wrote:
> On Apr 6, 2012, at 16:07, seattlelite (mailto:ryanac...@gmail.com)> wrote:
>
On Apr 6, 2012, at 16:07, seattlelite wrote:
> Question 1.
> I'm using Ruby 1.9.2, Rails 3.0.7 and I have RSpec and Autotest installed,
> but Autotest is not running my specs - it's running Unit:Test installed. How
> do I get it to run my Rspecs?
>
> I tried this:
>
> (a) http://blog.davidc
Question 1.
I'm using Ruby 1.9.2, Rails 3.0.7 and I have RSpec and Autotest installed,
but Autotest is not running my specs - it's running Unit:Test installed.
How do I get it to run my Rspecs?
I tried this:
(a) http://blog.davidchelimsky.net/2010/03/15/rspec-2-and-autotest/
Autotest.a
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
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
On Mar 17, 12:58 pm, ericindc wrote:
> I've included the output from running my specs with rake spec and
> autotest. I've restarted autotest several times to no avail. For
> some reason, autotest is missing the newsroom_blog_post specs. Any
> idea how to resolve this? I'd like to continue usin
I've included the output from running my specs with rake spec and
autotest. I've restarted autotest several times to no avail. For
some reason, autotest is missing the newsroom_blog_post specs. Any
idea how to resolve this? I'd like to continue using autotest, but
not if specs are going to be m
On Wed, Feb 2, 2011 at 6:24 PM, Trenton Scott wrote:
> >From my Rails project directory in Terminal, I'm able to run 'bundle
> exec rspec spec/' and it works successfully. When I try and run
> 'autotest', however, I get the error(s) below. Note: my .autotest file
> has require 'autotest/growl' and
>From my Rails project directory in Terminal, I'm able to run 'bundle
exec rspec spec/' and it works successfully. When I try and run
'autotest', however, I get the error(s) below. Note: my .autotest file
has require 'autotest/growl' and require 'autotest/fsevent' in it and
I have both installed.
I believe this is caused by a bad example on
https://github.com/rspec/rspec/wiki/autotest
,specifically under the section "Advanced autotest configuration".
I ran into this exact same issue and it was solved by changing the
example to use spec/**/*_spec.rb.
I went ahead and took the liberty of u
Thanks for your fast reply David,
> > The rake task requires spec/**/*.spec
>
> Close, but not quite. The default pattern is spec/**/*_spec.rb.
Typo sorry
>
> > Autotest rspec2 requires spec/**/*
>
> Again, this incorrect. Autotest fires off shell commands that include a list
> of files to load
On Jan 21, 2011, at 4:57 AM, Rob Westgeest wrote:
> On Nov 22 2010, 9:42 pm, LesFreeman wrote:
>> On Sep 28, 10:42 pm, Amiruddin Nagri wrote:
>>
>>> I am having asharedexample'allow authorized actions' for my Rails 3 RSpec
>>> 2.beta.20 application. Thesharedexamplelooks like
>>
>>> share_exam
I am having the same problem.
Autotest with rspec seem to differ from rspecs rake task in which
files to automatically require.
The rake task requires spec/**/*.spec
Autotest rspec2 requires spec/**/*
As I am sharing example groups in their own files names
(shared_*_examples.rb), and require the
I'm sure is not the best solution, but I solved the problem creating an
Initializer monkey patching the method giving the error. I'm pretty new
on Ruby and company, as always scratching the surface, and only now
getting into the deep, but I hope it will help.
# extract config/initializers/rspec
I too am having this error
On Sep 28, 10:42 pm, Amiruddin Nagri wrote:
> I am having a shared example 'allow authorized actions' for my Rails 3 RSpec
> 2.beta.20 application. The shared example looks like
>
> share_examples_for 'allow authorized actions' do
> ...
> end
>
> This shared example i
On Wed, Nov 10, 2010 at 6:29 PM, Jarmo Pertman wrote:
>
> Can you share some more (even technical) information about these
> solutions? Maybe through some other channel if this might get too
> offtopic in here...
>
Search ANSICON and win32console on Rubyinstaller group:
http://groups.google.com/
On Nov 10, 9:56 pm, Luis Lavena wrote:
> If you strip down the Bundler part, I'm under the same environment too :P
>
> While I can complain about Bundler doing weird things on Windows I
> decided to stop using it and switched to Isolate and invoke commands
> with "rake isolate:sh[autotest]"
I'm s
On Wed, Nov 10, 2010 at 3:43 PM, David Chelimsky wrote:
> On Nov 10, 2010, at 11:32 AM, Jarmo Pertman wrote:
>
>> Yup, understood and opened an issue in Bundler since it seems to be
>> the culprit in the end:
>> https://github.com/carlhuda/bundler/issues/issue/832
>>
>> Just FYI if there's any oth
On Nov 10, 2010, at 11:32 AM, Jarmo Pertman wrote:
> Yup, understood and opened an issue in Bundler since it seems to be
> the culprit in the end:
> https://github.com/carlhuda/bundler/issues/issue/832
>
> Just FYI if there's any other Windows/RSpec2/Autotest/Bundler user :)
Nope. Think you're t
Yup, understood and opened an issue in Bundler since it seems to be
the culprit in the end:
https://github.com/carlhuda/bundler/issues/issue/832
Just FYI if there's any other Windows/RSpec2/Autotest/Bundler user :)
Jarmo
On Nov 10, 5:23 pm, David Chelimsky wrote:
> On Nov 10, 2010, at 8:54 AM,J
On Nov 10, 2010, at 8:54 AM, Jarmo Pertman wrote:
> On Nov 10, 4:06 pm, David Chelimsky wrote:
>> On Nov 10, 2010, at 7:54 AM,JarmoPertmanwrote:
>>
>>> I didn't get any replies about that problem so far but i just managed
>>> to find out how to make it work manually.
>>
>> What manual change d
Ok, the path is coming from autotest.rb in autotest gem.
But i think that the bug is in Bundler instead:
C:\Users\jarmo\Desktop\minu\projects\Ruby\sample_app>bundle exec c:
\Ruby\bin\ruby --version
bundler: command not found: c:\Ruby\bin\ruby
Install missing gem binaries with `bundle install`
C:\
On Nov 10, 4:06 pm, David Chelimsky wrote:
> On Nov 10, 2010, at 7:54 AM,JarmoPertmanwrote:
>
> > I didn't get any replies about that problem so far but i just managed
> > to find out how to make it work manually.
>
> What manual change did you make?
>
> > The problem is that the bundle exec is no
On Nov 10, 2010, at 7:54 AM, Jarmo Pertman wrote:
> I didn't get any replies about that problem so far but i just managed
> to find out how to make it work manually.
What manual change did you make?
> The problem is that the bundle exec is not working like this on
> Windows:
> bundle exec C:\bin
I didn't get any replies about that problem so far but i just managed
to find out how to make it work manually.
The problem is that the bundle exec is not working like this on
Windows:
bundle exec C:\bin\pik\Ruby-187-p302\bin\ruby
But works like this:
bundle exec C:\bin\pik\Ruby-187-p302\bin\ruby
Hi *, I'm trying to implement the Warden middleware, but apparently warden is
making autotest crash.
Here is the backtrace:
https://gist.github.com/657378/a2c8fc15a179331d23f9015a6aba75a0a635121f
Specs and features run as normal.
This is what is in strategies.rb: https://gist.github.com/663795
I have the same problem with the combination above with Ruby 1.9.2 on
Windows XP, as described here:
http://www.ruby-forum.com/topic/205569
Calling Rspec directly produces colored output, but autotest spits out
ANSI sequences. The issue was supposed to be closed with win32console
1.3.0, but obviou
Hello. I've been trying for the last 2 days to make autotest with rspec2
send notifications on windows7 but without any success.
First i used only the autotest gem with autotest-growl and the latest
version of growl for windows including the growlnotifier. Made all the
proper adjustments : created
No ideas, what might cause that problem? Could it be a Windows-only-
issue?
Jarmo
On Oct 22, 3:46 pm, Jarmo Pertman wrote:
> Hello!
>
> I'm trying to run autotest under Windows when using Rails 3.0.1 and
> RSpec 2.0.1. It's not working so far. This is what happens:
> C:\Users\jarmo\Desktop\minu\
Hello!
I'm trying to run autotest under Windows when using Rails 3.0.1 and
RSpec 2.0.1. It's not working so far. This is what happens:
C:\Users\jarmo\Desktop\minu\projects\Ruby\sample_app>autotest
loading autotest/rails_rspec2
style: RailsRspec2
bundle exec C:\bin\pik\Ruby-187-p302\bin\ruby -S C:/
I am having a shared example 'allow authorized actions' for my Rails 3 RSpec
2.beta.20 application. The shared example looks like
share_examples_for 'allow authorized actions' do
...
end
This shared example is in file
spec/controllers/support/authorization_shared_example.rb, which I am
requirin
On Sep 18, 2010, at 5:51 AM, Brennon Bortz wrote:
> On 18 Sep 2010, at 11:20, Brennon Bortz wrote:
>
>> On 17 Sep 2010, at 20:11, David Chelimsky wrote:
>>
>>> On Sep 17, 2010, at 1:23 PM, Brennon Bortz wrote:
>>>
On 14 Sep 2010, at 22:41, Brennon Bortz wrote:
> On 27 Aug 2010,
On 18 Sep 2010, at 11:20, Brennon Bortz wrote:
> On 17 Sep 2010, at 20:11, David Chelimsky wrote:
>
>> On Sep 17, 2010, at 1:23 PM, Brennon Bortz wrote:
>>
>>> On 14 Sep 2010, at 22:41, Brennon Bortz wrote:
>>>
On 27 Aug 2010, at 15:20, David Chelimsky wrote:
>
> On Aug 27,
On 17 Sep 2010, at 20:11, David Chelimsky wrote:
> On Sep 17, 2010, at 1:23 PM, Brennon Bortz wrote:
>
>> On 14 Sep 2010, at 22:41, Brennon Bortz wrote:
>>
>>> On 27 Aug 2010, at 15:20, David Chelimsky wrote:
>>>
On Aug 27, 2010, at 8:48 AM, Brennon Bortz wrote:
> On 27 Au
On Sep 17, 2010, at 1:23 PM, Brennon Bortz
wrote:
On 14 Sep 2010, at 22:41, Brennon Bortz wrote:
On 27 Aug 2010, at 15:20, David Chelimsky wrote:
On Aug 27, 2010, at 8:48 AM, Brennon Bortz wrote:
On 27 Aug 2010, at 14:44, David Chelimsky wrote:
On Aug 27, 2010, at 8:37 AM, Brennon Bo
On 14 Sep 2010, at 22:41, Brennon Bortz wrote:
> On 27 Aug 2010, at 15:20, David Chelimsky wrote:
>
>>
>> On Aug 27, 2010, at 8:48 AM, Brennon Bortz wrote:
>>
>>> On 27 Aug 2010, at 14:44, David Chelimsky wrote:
>>>
On Aug 27, 2010, at 8:37 AM, Brennon Bortz wrote:
> On 27 Aug 2
On 27 Aug 2010, at 15:20, David Chelimsky wrote:
>
> On Aug 27, 2010, at 8:48 AM, Brennon Bortz wrote:
>
>> On 27 Aug 2010, at 14:44, David Chelimsky wrote:
>>
>>> On Aug 27, 2010, at 8:37 AM, Brennon Bortz wrote:
>>>
On 27 Aug 2010, at 14:29, Brennon Bortz wrote:
> On 27 Aug 20
On Aug 27, 2010, at 8:06 AM, David Chelimsky wrote:
> On Aug 27, 2010, at 6:47 AM, Brennon Bortz wrote:
>
>> Not sure what I must have bumped, but autotest won't run any specs--only
>> features. No errors are given on startup. I've taken "export
>> AUTOFEATURE=true" out of my ./bashrc file--n
On Aug 27, 2010, at 8:48 AM, Brennon Bortz wrote:
> On 27 Aug 2010, at 14:44, David Chelimsky wrote:
>
>> On Aug 27, 2010, at 8:37 AM, Brennon Bortz wrote:
>>
>>> On 27 Aug 2010, at 14:29, Brennon Bortz wrote:
>>>
On 27 Aug 2010, at 14:06, David Chelimsky wrote:
> On Aug 27, 201
On 27 Aug 2010, at 14:44, David Chelimsky wrote:
> On Aug 27, 2010, at 8:37 AM, Brennon Bortz wrote:
>
>> On 27 Aug 2010, at 14:29, Brennon Bortz wrote:
>>
>>> On 27 Aug 2010, at 14:06, David Chelimsky wrote:
>>>
On Aug 27, 2010, at 6:47 AM, Brennon Bortz wrote:
> Not sure what I
On Aug 27, 2010, at 8:37 AM, Brennon Bortz wrote:
> On 27 Aug 2010, at 14:29, Brennon Bortz wrote:
>
>> On 27 Aug 2010, at 14:06, David Chelimsky wrote:
>>
>>> On Aug 27, 2010, at 6:47 AM, Brennon Bortz wrote:
>>>
Not sure what I must have bumped, but autotest won't run any specs--only
>>
And now (I haven't touched anything...seriously!), even "AUTOFEATURE=false
autotest" gives me an endless loop of spec tests...
On 27 Aug 2010, at 14:29, Brennon Bortz wrote:
> Strange...that does work, but now autotest seems caught in an infinite loop.
> When I run autospec, the specs run, the
Strange...that does work, but now autotest seems caught in an infinite loop.
When I run autospec, the specs run, then the features, then the features
again...and again...and again...and so on. If I run autotest as follows:
"AUTOFEATURE=false autotest", I don't have the problem. Any other idea
On Aug 27, 2010, at 6:47 AM, Brennon Bortz wrote:
> Not sure what I must have bumped, but autotest won't run any specs--only
> features. No errors are given on startup. I've taken "export
> AUTOFEATURE=true" out of my ./bashrc file--now I just get a blank screen when
> running autotest. Addi
I should point out that autotest detects changes to specs just fine and reloads
accordingly--but still only gives blank output.
Thanks again,
Brennon
Brennon Bortz
Software Researcher
Dundalk Institute of Technology
brennon.bo...@casala.ie
Ph.D. Researcher & Composer - Sonic Arts Research Centre
Not sure what I must have bumped, but autotest won't run any specs--only
features. No errors are given on startup. I've taken "export
AUTOFEATURE=true" out of my ./bashrc file--now I just get a blank screen when
running autotest. Adding "export RSPEC=true" to .bashrc doesn't change
anything
On Aug 18, 2010, at 8:28 AM, David Chelimsky wrote:
> On Aug 18, 2010, at 3:56 AM, Nils Riedemann wrote:
>
>>
>> On 18 Aug., 07:29, David Chelimsky wrote:
>>> On Aug 17, 2010, at 3:18 AM, Nils Riedemann wrote:
>>>
>>>
>>>
>>>
>>>
Hi there,
>>>
When i run `rspec --drb spec` ever
On Aug 18, 2010, at 3:56 AM, Nils Riedemann wrote:
>
> On 18 Aug., 07:29, David Chelimsky wrote:
>> On Aug 17, 2010, at 3:18 AM, Nils Riedemann wrote:
>>
>>
>>
>>
>>
>>> Hi there,
>>
>>> When i run `rspec --drb spec` everything works fine. Yet, when i want
>>> to use `autotest` it outputs
On 18 Aug., 07:29, David Chelimsky wrote:
> On Aug 17, 2010, at 3:18 AM, Nils Riedemann wrote:
>
>
>
>
>
> > Hi there,
>
> > When i run `rspec --drb spec` everything works fine. Yet, when i want
> > to use `autotest` it outputs the following:
>
> > ~/code/ffr[master]% autotest
> > /Users/ni
On Aug 17, 2010, at 3:18 AM, Nils Riedemann wrote:
> Hi there,
>
> When i run `rspec --drb spec` everything works fine. Yet, when i want
> to use `autotest` it outputs the following:
>
>~/code/ffr[master]% autotest
>/Users/nilsriedemann/.rvm/rubies/ruby-1.9.2-rc2/lib/ruby/1.9.1/
> rubyge
Hi there,
When i run `rspec --drb spec` everything works fine. Yet, when i want
to use `autotest` it outputs the following:
~/code/ffr[master]% autotest
/Users/nilsriedemann/.rvm/rubies/ruby-1.9.2-rc2/lib/ruby/1.9.1/
rubygems.rb:1051: warning: method redefined; discarding old gem
:15:
On 14 Aug 2010, at 18:49, Don French wrote:
> Thought that was what you meant, but did not want to leave anything
> untried. I have updated to 1.9.2-rc2. same problem. I am going to
> have to do an update to snow leopard soon, may try it and put new code
> on not just restore.
I wish I could he
Thought that was what you meant, but did not want to leave anything
untried. I have updated to 1.9.2-rc2. same problem. I am going to
have to do an update to snow leopard soon, may try it and put new code
on not just restore.
Don French
On Aug 14, 4:40 am, Ashley Moran
wrote:
> On 13 Aug 2010,
On 13 Aug 2010, at 22:16, Don French wrote:
> Not sure what you meant by "did you turn it off and on again?"
Ah, I just meant I was running out of ideas[1].
> The other information is here:
> http://pastie.org/1091155
All I can suggest is maybe updating RVM and trying in Ruby 1.9.2 with a fre
I converted from rspec 1.3 to rspec 2
On Aug 13, 5:50 am, Ashley Moran
wrote:
> On Aug 12, 2010, at 11:09 pm, Don French wrote:
>
> > yep: Autotest.add_discovery {"rspec2"}
> > in the base project directory
>
> I'm at the point of asking "did you turn it off and on again?" :-/
>
> Can you give y
Not sure what you meant by "did you turn it off and on again?"
The other information is here:
http://pastie.org/1091155
Don French
On Aug 13, 5:50 am, Ashley Moran
wrote:
> On Aug 12, 2010, at 11:09 pm, Don French wrote:
>
> > yep: Autotest.add_discovery {"rspec2"}
> > in the base project di
On Aug 12, 2010, at 11:09 pm, Don French wrote:
> yep: Autotest.add_discovery {"rspec2"}
> in the base project directory
I'm at the point of asking "did you turn it off and on again?" :-/
Can you give your Ruby installation details? (versions etc, ideally the output
of `rvm info` and `gem li
yep: Autotest.add_discovery {"rspec2"}
in the base project directory
dhf
On Aug 12, 11:32 am, David Chelimsky wrote:
> On Aug 12, 2010, at 4:02 PM, Don French wrote:
>
> > There are lots of spec files. I can run them using rspec spec and
> > everything is great. just the autotest does not work.
On Aug 12, 2010, at 4:02 PM, Don French wrote:
> There are lots of spec files. I can run them using rspec spec and
> everything is great. just the autotest does not work.
> Don French
Did you create autotest/discover.rb?
http://blog.davidchelimsky.net/2010/03/15/rspec-2-and-autotest/
>
> On Au
There are lots of spec files. I can run them using rspec spec and
everything is great. just the autotest does not work.
Don French
On Aug 12, 10:48 am, Don French wrote:
> put in
> $:.unshift(File.dirname(__FILE__) + '/../lib')
> require 'reader'
> and get the same thing
>
> dhf
>
> On Aug 12, 10
I put in:
$:.unshift(File.dirname(__FILE__) + '/../lib')
require 'reader'
and it still does nothing.
dhf
On Aug 12, 10:13 am, David Chelimsky wrote:
> On Aug 12, 2010, at 3:08 PM, Don French wrote:
>
> > The helper file does not have anything in it as of right now. It had
> > the the old
> >
put in
$:.unshift(File.dirname(__FILE__) + '/../lib')
require 'reader'
and get the same thing
dhf
On Aug 12, 10:13 am, David Chelimsky wrote:
> On Aug 12, 2010, at 3:08 PM, Don French wrote:
>
> > The helper file does not have anything in it as of right now. It had
> > the the old
> > #begin
>
On Aug 12, 2010, at 3:08 PM, Don French wrote:
> The helper file does not have anything in it as of right now. It had
> the the old
> #begin
> # require 'spec'
> #rescue LoadError
> # require 'rubygems' unless Config['NO_RUBYGEMS']
> # gem 'rspec'
> # require 'spec'
> #end
> from rspec 1.3.0
rspec spec works fine and provides test results.
The helper file does not have anything in it. It had the the old
#begin
# require 'spec'
#rescue LoadError
# require 'rubygems' unless Config['NO_RUBYGEMS']
# gem 'rspec'
# require 'spec'
#end
from rspec 1.3.0
Now it is empty. This project
The helper file does not have anything in it as of right now. It had
the the old
#begin
# require 'spec'
#rescue LoadError
# require 'rubygems' unless Config['NO_RUBYGEMS']
# gem 'rspec'
# require 'spec'
#end
from rspec 1.3.0
Now it is empty. This project was generated via newgem.
I want
On 12 Aug 2010, at 08:27, Don French wrote:
> under bundler bundle exec autotest standalone autotest both within
> the project directory and there is a spec subdirectory with the spec
> in them.
What happens when you run `rspec spec`?
What is in your spec_helper.rb file?
What is the output of
under bundler bundle exec autotest standalone autotest both within
the project directory and there is a spec subdirectory with the spec
in them.
On Aug 11, 1:14 pm, David Chelimsky wrote:
> On Aug 11, 2010, at 4:54 PM, Don French wrote:
>
> > That is correct. No tests are run. Just get the OS c
On Aug 11, 2010, at 4:54 PM, Don French wrote:
> That is correct. No tests are run. Just get the OS command prompt
> back.
You said in an earlier post that this happens whether you run this under
bundler or not. What, precisely, are the commands you're using?
> Don French
>
>
> On Aug 11, 8:4
That is correct. No tests are run. Just get the OS command prompt
back.
Don French
On Aug 11, 8:49 am, Ashley Moran
wrote:
> On 11 Aug 2010, at 19:44, Don French wrote:
>
> > Any help on this. I think I have read all posts related to autotest
> > but still do not have the answer. Is there somet
On 11 Aug 2010, at 19:44, Don French wrote:
> Any help on this. I think I have read all posts related to autotest
> but still do not have the answer. Is there something that works better
> with Rspec that autotest?
When you say "and a prompt (back)" ... do you mean autotest exits in both
situat
Any help on this. I think I have read all posts related to autotest
but still do not have the answer. Is there something that works better
with Rspec that autotest?
Don French
On Aug 10, 4:24 pm, Don French wrote:
> I have a non rails app using rspec2. I created the autotest/
> discover.rb and
I have a non rails app using rspec2. I created the autotest/
discover.rb and put in it Autotest.add_discovery {"rspec2"}. When I
run under bundler I get -
loading autotest/rspec2
and a prompt back
When standalone I get:
loading autotest/rspec2
style: Rspec2
and a prompt. Any ideasas to the pr
On Sun, Jun 27, 2010 at 8:14 PM, Don French wrote:
> On Jun 27, 2:09 pm, David Chelimsky wrote:
>> On Jun 27, 2010, at 6:51 PM, Don French wrote:
>>
>> > I am trying to use rspec2 rails with rails3 beta 4. I created a simple
>> > project and a couple of models. The basic test spec files are there
Sure did. Just ran it again:
identical .rspec
exist spec
identical spec/spec_helper.rb
exist lib
identical lib/tasks/rspec.rake
identical config/initializers/rspec_generator.rb
exist autotest
identical autotest/discover.rb
I am running everything under b
On Jun 27, 2010, at 6:51 PM, Don French wrote:
> I am trying to use rspec2 rails with rails3 beta 4. I created a simple
> project and a couple of models. The basic test spec files are there.
> When I run bundle spec:models I get what I expect. When I run bundle
> autotest I get:
>
> mauidev:testm
I am trying to use rspec2 rails with rails3 beta 4. I created a simple
project and a couple of models. The basic test spec files are there.
When I run bundle spec:models I get what I expect. When I run bundle
autotest I get:
mauidev:testme dhf$ bundle exec autotest
loading autotest/rails_rspec2
ma
More FYI: Ryan released ZenTest 4.3.1 yesterday to address this issue,
so you can upgrade to the latest and greatest.
On Tue, Mar 30, 2010 at 2:53 PM, David Chelimsky wrote:
> FYI - I uninstalled ZenTest-4.3.0 and installed ZenTest-4.2.1 and all is well:
>
> [sudo] gem uninstall ZenTest
> [sudo]
FYI - I uninstalled ZenTest-4.3.0 and installed ZenTest-4.2.1 and all is well:
[sudo] gem uninstall ZenTest
[sudo] gem install ZenTest --version 4.2.1
HTH,
David
On Tue, Mar 30, 2010 at 12:44 PM, Matthew O'riordan
wrote:
> Hi Edgar
>
> I think the error you are saying is a direct result of you
Hi Edgar
I think the error you are saying is a direct result of you hitting Ctl-C
in that you are killing the process and thus the output. Could be
wrong, but I suspect that's the issue. I get different error messages
every time I hit Ctl-C depending on where in the test execution autotest
i
Please see (and comment on) the bug report for autotest-rails that Matt raised:
http://rubyforge.org/tracker/index.php?func=detail&aid=28034&group_id=419&atid=1678
On Mar 30, 2010, at 12:21 PM, Edgar Gonzalez wrote:
> Hi Matt,
>
> I have the same misbehavior after update the gems,the autotest's
Hi Matt,
I have the same misbehavior after update the gems,the autotest's output is
garbled and if I hit Ctrl-C once (to run the specs again) I got this error:
usr/lib/ruby/gems/1.8/gems/rspec-1.3.0/lib/spec/runner/formatter/progress_bar_formatter.rb:16:in
`write': Broken pipe (Errno::EPIPE)
I recently reinstalled my gems for autotest, and since then I have
unintelligible output coming from autotest like this (note everything
after unit_diff -u)
loading autotest/rails
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
-I.:lib:test -rubygems -e "%w[test/unit test/unit/
Hi,
I've read in [1] that autotest "does not work with view specs for rails
versions < 2.3", but I didn't find a reason for that.
Is it just a bug?
--
[]'s Bruno
[1] http://wiki.github.com/dchelimsky/rspec/spork-autospec-pure-bdd-joy
--
[]'s Bruno
_
On Sun, Mar 21, 2010 at 8:08 PM, Bruno Pedroso wrote:
> Hi,
>
> I've read in [1] that autotest "does not work with view specs for rails
> versions < 2.3", but I didn't find a reason about that.
It's the combination of autotest and spork that results in inconsistent results.
> Is it just a bug?
Hi,
I've read in [1] that autotest "does not work with view specs for rails
versions < 2.3", but I didn't find a reason about that.
Is it just a bug?
--
[]'s Bruno
[1] http://wiki.github.com/dchelimsky/rspec/spork-autospec-pure-bdd-joy
___
rspec-us
Cool, thanks!
Regards,
Jeroen
On Mar 14, 4:11 pm, David Chelimsky wrote:
> On Mar 14, 2010, at 5:12 AM, Jeroen wrote:
>
> > Hi guys,
>
> > I'm trying to find some information on how to get autotest to run the
> > rspec2 tests. I have my project setup so "rake spec" runs the specs
> > properly, b
On Mar 14, 2010, at 5:12 AM, Jeroen wrote:
> Hi guys,
>
> I'm trying to find some information on how to get autotest to run the
> rspec2 tests. I have my project setup so "rake spec" runs the specs
> properly, but autotest seems to ignore/don't know that there are specs
> to test.
>
> I read on
Hi guys,
I'm trying to find some information on how to get autotest to run the
rspec2 tests. I have my project setup so "rake spec" runs the specs
properly, but autotest seems to ignore/don't know that there are specs
to test.
I read on the rspec2 wiki that autotest integration is o be added
even
On Thu, May 21, 2009 at 10:34 AM, Kero van Gelder wrote:
>> >> > Is there some configuration I need to do to get rid of unit/functional
>> >> > tests and only run rspec+cucumber?
>> >
>> > [...]
>> >> I guess I should add this in some form to the rspec wiki ;)
>> >
>> > Done:
>> > http://wiki.gi
> >> > Is there some configuration I need to do to get rid of unit/functional
> >> > tests and only run rspec+cucumber?
> >
> > [...]
> >> I guess I should add this in some form to the rspec wiki ;)
> >
> > Done:
> > http://wiki.github.com/dchelimsky/rspec/autotest-integration
>
> Thanks Kero. I
Kero van Gelder wrote:
Is there some configuration I need to do to get rid of unit/functional
tests and only run rspec+cucumber?
[...]
I guess I should add this in some form to the rspec wiki ;)
Done:
http://wiki.github.com/dchelimsky/rspec/autotest-integration
+1.
On Thu, May 21, 2009 at 2:27 AM, Kero van Gelder wrote:
>> > Is there some configuration I need to do to get rid of unit/functional
>> > tests and only run rspec+cucumber?
>
> [...]
>> I guess I should add this in some form to the rspec wiki ;)
>
> Done:
> http://wiki.github.com/dchelimsky/rspec
Cool. Scott, Kero -- thanks.
dwh
Kero van Gelder wrote:
Is there some configuration I need to do to get rid of unit/functional
tests and only run rspec+cucumber?
[...]
I guess I should add this in some form to the rspec wiki ;)
Done:
http://wiki.github.com/dchelimsky/rs
> > Is there some configuration I need to do to get rid of unit/functional
> > tests and only run rspec+cucumber?
[...]
> I guess I should add this in some form to the rspec wiki ;)
Done:
http://wiki.github.com/dchelimsky/rspec/autotest-integration
Bye,
Kero.
___
How can I change the world
> Is there some configuration I need to do to get rid of unit/functional
> tests and only run rspec+cucumber?
This eplains all there is to explain (though terse and not from
your use case)
http://zentest.rubyforge.org/ZenTest/Autotest.html
and you now have to add code from that to your .auto
Denis Haskin wrote:
Thanks. Ok -- removing grosser-autotest lets autotest run, but it's
only running my unit tests, not rspec:
$ autotest
(Not running features. To run features in autotest, set
AUTOFEATURE=true.)
loading autotest/rails
/usr/bin/ruby1.8 -I.:lib:test -rubygems -e "%w[test/uni
Thanks. Ok -- removing grosser-autotest lets autotest run, but it's
only running my unit tests, not rspec:
$ autotest
(Not running features. To run features in autotest, set AUTOFEATURE=true.)
loading autotest/rails
/usr/bin/ruby1.8 -I.:lib:test -rubygems -e "%w[test/unit
test/unit/design_tes
Denis Haskin wrote:
I didn't have ZenTest installed. I just did, but I still get the same
error. Should I *not* have grosser-autotest installed?
$ gem list | grep -i test
grosser-autotest (4.0.4)
test-unit (2.0.2)
ZenTest (4.0.0)
Try removing it.
Make sure to grab the latest ZenTest (which
I didn't have ZenTest installed. I just did, but I still get the same
error. Should I *not* have grosser-autotest installed?
$ gem list | grep -i test
grosser-autotest (4.0.4)
test-unit (2.0.2)
ZenTest (4.0.0)
dwh
Scott Taylor wrote:
Denis Haskin wrote:
Hmm. Okay, tried that but:
$ autos
Denis Haskin wrote:
Hmm. Okay, tried that but:
$ autospec
(Not running features. To run features in autotest, set
AUTOFEATURE=true.)
loading autotest/rails_rspec
Autotest style autotest/rails_rspec doesn't seem to exist. Aborting.
I'm running my rails rspec examples just fine manually...
d
1 - 100 of 243 matches
Mail list logo
