On Oct 30, 2007 7:05 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
> Hi
>
> I can't get heckle working. In fact, I've built an example so simple
> that it either shows a bug, or I am being really, REALLY stupid.
Heckle is hosed in trunk. We'll get it fixed before the release. Of
course, that means
On Oct 31, 2007 6:28 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Oct 30, 2007 7:05 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I can't get heckle working. In fact, I've built an example so simple
> > that it either shows a bug, or I am being really, REALLY stupid.
>
> Heckle
Hey, I'm trying to configure autotest with rspec on cygwin but something is
going wrong.
I made a very simple testing environment with a user.rb and user_spec.rb
file. Rspec works fine, but autotest outputs nothing - it just stays here,
idle. ^C doesn't display anything more.
I can see it's runn
El 31/10/2007, a las 15:40, "David Chelimsky" <[EMAIL PROTECTED]>
escribió:
> On Oct 30, 2007 7:05 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
>> Hi
>>
>> I can't get heckle working. In fact, I've built an example so simple
>> that it either shows a bug, or I am being really, REALLY stupid.
>
>
On Oct 31, 2007 9:56 AM, Wincent Colaiuta <[EMAIL PROTECTED]> wrote:
> El 31/10/2007, a las 15:40, "David Chelimsky" <[EMAIL PROTECTED]>
> escribió:
> Recently with all of the activity on the story runner front I've
> thought that RSpec could benefit from a slightly more "branched"
> development pr
On Oct 31, 2007 9:30 AM, pangel <[EMAIL PROTECTED]> wrote:
>
> Hey, I'm trying to configure autotest with rspec on cygwin but something is
> going wrong.
>
> I made a very simple testing environment with a user.rb and user_spec.rb
> file. Rspec works fine, but autotest outputs nothing - it just sta
As you are on Windows can I suggest you try removing all of the options from
your spec.opts file and try again. You need to do this with native windows
but not sure about cygwin.
Worth a try.
On 10/31/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> On Oct 31, 2007 9:30 AM, pangel <[EMAIL PROTE
On Oct 31, 2007 10:44 AM, Lee Irving <[EMAIL PROTECTED]> wrote:
> As you are on Windows can I suggest you try removing all of the options from
> your spec.opts file
Or you can just remove that file :)
> and try again. You need to do this with native windows
> but not sure about cygwin.
>
> Worth
On Oct 31, 2007, at 7:28 AM, David Chelimsky wrote:
> On Oct 30, 2007 7:05 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
>> Hi
>>
>> I can't get heckle working. In fact, I've built an example so simple
>> that it either shows a bug, or I am being really, REALLY stupid.
>
> Heckle is hosed in trunk
Just upgraded to latest rails and rspec builds and my autotest doesnt
work
undefined method `before' for Spec::Rails::DSL::RailsExample:Class
(NoMethodError)
Here's the full trace:
http://pastie.caboo.se/112754
Any ideas?
--
Posted via http://www.ruby-forum.com/.
__
From a previous post - the bottom line is that even in Cygwin,
File::ALT_SEPARATOR returns "\". In autotest.rb (under ZenTest/lib), the
method named "ruby" which attempts to return the path to the executable
doesn't work correctly on Windows.
See below.
I ran into this as well - see my posts
On Oct 31, 2007 11:36 AM, Scott Taylor <[EMAIL PROTECTED]> wrote:
> When can we expect the next release of rspec?
Definitely by the end of November.
Likely by mid-November.
Hopefully in a matter of days.
The next release will be 1.1.0.
We're going to a release model in which 1.odd.x will be cons
Pangel,
I run autotest on cygwin so it can work ... :)
Does rake spec work ?
Have you installed all gems in cygwin ?
How are you starting autotest ?
On 10/31/07, pangel <[EMAIL PROTECTED]> wrote:
>
>
> I am quite a beginner so maybe I'm not looking into the right place, but I
> don'
On Oct 31, 2007 11:34 AM, Steven Garcia <[EMAIL PROTECTED]> wrote:
> Just upgraded to latest rails and rspec builds and my autotest doesnt
> work
>
> undefined method `before' for Spec::Rails::DSL::RailsExample:Class
> (NoMethodError)
>
> Here's the full trace:
>
> http://pastie.caboo.se/112754
sc
I did that.. still getting the same error
funky
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
I just did the modification and the problem remains.
Is there a way to output the final value of the ruby variable so I can check
if it matches the actual path to ruby?
Wes Gamble wrote:
>
> From a previous post - the bottom line is that even in Cygwin,
> File::ALT_SEPARATOR returns "\". In
I am quite a beginner so maybe I'm not looking into the right place, but I
don't think I have a spec.opts file.
The same problem (ie no output with autotest) happens with Test::Unit.
As a cygwin user, do I still need win32console? Just occured to me.
Also, to make sure I didn't forget something
One last thing - ensure that there is no "--colour" option in your
spec.opts. Don't know why it matters but it does.
Throw a quick "puts" into autotest.rb to verify the value of the ruby
variable.
Wes
pangel wrote:
> I just did the modification and the problem remains.
>
> Is there a way to o
It works! I simply created a /spec directory and moved user_spec.rb to
/spec/spec_user.rb
I'll stick with this solution for now. The integration with snarl is alright
just not perfectly stable, sometimes snarl 'forgets' to signal me a change
in the test results.
Anyway, to answer your questions:
I put together a simple tutorial showing how I use Hpricot to tests my "XML
views"
http://railsontherun.com/2007/10/31/how-to-test-a-xml-builder-view
I'm sure there are other ways and even maybe something built in RSpec.
Anyone knows of a "better" solution?
Thanks,
-Matt
--
--
On Oct 31, 2007, at 12:15 pm, David Chelimsky wrote:
> Fixed in r2803.
Excellent, thanks! However it still runs heckle even if the specs
fail (and then assumes that the heckling is successful, because of the
failing spec).
Also I notice that, as long as the specs pass, the return code for
On Oct 31, 2007 1:50 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
>
> On Oct 31, 2007, at 12:15 pm, David Chelimsky wrote:
>
> > Fixed in r2803.
>
> Excellent, thanks! However it still runs heckle even if the specs
> fail (and then assumes that the heckling is successful, because of the
> failing s
On Oct 31, 2007, at 4:36 pm, Scott Taylor wrote:
> When can we expect the next release of rspec?
You wait for *releases*? :)
--
blog @ http://aviewfromafar.net/
linked-in @ http://www.linkedin.com/in/ashleymoran
currently @ home
___
rspec-users mai
On Oct 31, 2007, at 4:53 pm, David Chelimsky wrote:
> We're going to a release model in which 1.odd.x will be considered
> experimental. This means that while we will document code-breaking
> changes in subsequent releases (so you know what to do to move
> forward), we will not commit to backward
Downgraded to Stable on both rspec and rails and its workin fine.
Weird spooky stuff goin on in that trunk!
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-user
On Oct 31, 2007, at 2:50 PM, Ashley Moran wrote:
>
> On Oct 31, 2007, at 4:36 pm, Scott Taylor wrote:
>
>> When can we expect the next release of rspec?
>
> You wait for *releases*? :)
No, we are running on trunk, but have had a number of frustrating
days. I'm the one who advocates rspec, and
On Oct 31, 2007 1:52 PM, Steven Garcia <[EMAIL PROTECTED]> wrote:
> Downgraded to Stable on both rspec and rails and its workin fine.
>
> Weird spooky stuff goin on in that trunk!
Looking back at your pastie (http://pastie.caboo.se/112754) I see the
problem. There are references to two different r
On Oct 31, 2007, at 11:56 AM, Ashley Moran wrote:
>
> On Oct 31, 2007, at 4:53 pm, David Chelimsky wrote:
>
>> We're going to a release model in which 1.odd.x will be considered
>> experimental. This means that while we will document code-breaking
>> changes in subsequent releases (so you know wh
One final note.. autotest is working fine, but when I quit, I get a
bunch of Zentest errors. Not a big deal, but worth noting:
/usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/autotest.rb:242:in
`add_sigint_handler': Interrupt (Interrupt)
from /usr/local/lib/ruby/1.8/find.rb:43:in `ca
On Oct 31, 2007 1:56 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
> I've always been puzzled by this way of handling beta releases, which
> quite a few open source projects follow. What's the thinking behind a
> 1.odd, 1.even pattern, as opposed to offering 1.x and trunk?
Interestingly enough, the
On 30/10/2007, at 10:58 AM, Lance Carlson wrote:
> MiddleMan = Object.new
>
> at the top of my spec file worked better for me. I didn't want to have
> to mess with ENV variables.
>
>
Hi Guys
This solution seemed to work nicely ... I was getting warnings about
redefining the constant and so ad
Argh... dont know how I missed something so obvious.
I reinstalled both from trunk and autotest is bouncing along as usual.
Thanks for the assist!
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://r
On Oct 31, 2007, at 6:53 pm, David Chelimsky wrote:
> Tickets would be awesome. Please reference the revision number you're
> working from.
Sure thing - they've gone up as two separate issues
So by the time RSpec 1.2 comes out, and specs, stories, rcov and
heckle are all working seamlessly, t
On Oct 31, 2007 3:48 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
>
> On Oct 31, 2007, at 6:53 pm, David Chelimsky wrote:
>
> > Tickets would be awesome. Please reference the revision number you're
> > working from.
>
> Sure thing - they've gone up as two separate issues
>
> So by the time RSpec 1.2
On Oct 31, 2007, at 6:58 pm, Scott Taylor wrote:
> No, we are running on trunk, but have had a number of frustrating
> days. I'm the one who advocates rspec, and when running on trunk
> starts bothering my co-workers, it makes me look bad.
Ah, I know where you are coming from. Shame no-one els
On Oct 31, 2007 3:56 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
>
> On Oct 31, 2007, at 6:58 pm, Scott Taylor wrote:
>
> > No, we are running on trunk, but have had a number of frustrating
> > days. I'm the one who advocates rspec, and when running on trunk
> > starts bothering my co-workers, it
On Oct 31, 2007, at 8:52 pm, David Chelimsky wrote:
> If you think having the right tools will make you right perfect
> code ...
Nope, they won't *make* me... but if I'm trying, and the tools both
facilitate the effort and tell me when I mess up, surely that goes a
very long way?
I mean,
On Oct 31, 2007 4:20 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
> It's like leaving things you need to take to work next to your car keys.
If only I could remember where I put the damned car keys!
___
rspec-users mailing list
rspec-users@rubyforge.org
h
Great!
/spec
/controllers
/models
/helpers
/views
is a common way to organize the specs
--
Cheers!
sinclair
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyfo
On 29/10/2007, at 11:27 AM, Ashley Moran wrote:
>
> But then it keeps nagging me:
>/spec/celestial/engine/connections/sqlite_connection_spec.rb:14:
>warning: already initialized constant SQLite3
>
Similar to my MiddleMan stub I used
class Object; remove_const :MiddleMan; end
Not s
You too!
On Oct 31, 2007, at 2:25 PM, David Chelimsky wrote:
> On Oct 31, 2007 4:20 PM, Ashley Moran <[EMAIL PROTECTED]> wrote:
>> It's like leaving things you need to take to work next to your car
>> keys.
>
> If only I could remember where I put the damned car keys!
> _
On Oct 31, 2007, at 9:59 pm, Shane Mingins wrote:
> Similar to my MiddleMan stub I used
>
> class Object; remove_const :MiddleMan; end
>
> Not sure how kosha it is?
Hi Shane
That was my actually my solution in the end, but I didn't post back to
the list. To be honest, I don't think an
Fellow hecklers,
Just spent a while getting this working. Turns out heckle will heckle
a whole module and sub-modules with one call, so with a bit of string
matching, you can build a nice tool to heckle your whole app and
report any failures.
Was going to post to the list, as the first ver
On Mon, 29 Oct 2007 23:31:37 -0700, Brian Takita wrote:
> I have to confess that I did not know about facets before reading
> Ashley Moran's post:
> http://aviewfromafar.net/2007/10/21/quick-and-dirty-facets-in-rspec-trunk
>
> Not knowing about the facets solution, I made a couple of feature
> re
I followed this step by step:
Object.class_eval { remove_const :RMovie }
@ffm = mock("RMovie Movie Class")
RMovie = Module.new
RMovie::Movie = Class.new
RMovie::Movie.stub!(:new).and_return(@ffm)
and I got a 'stack level too deep' error on the last line. Anyone have
any idea
Nevermind, my bad.. the test was perfect.. my code was doing something crazy
On 10/31/07, Lance Carlson <[EMAIL PROTECTED]> wrote:
> I followed this step by step:
>
> Object.class_eval { remove_const :RMovie }
>
> @ffm = mock("RMovie Movie Class")
>
> RMovie = Module.new
> RMovie::
46 matches
Mail list logo
