[rspec-devel] [rspec-users] Getting RSpec 1.1.4+ to Work with Autotest (ZenTest 3.10.0) on Windows (Win32)
dchelimsky at gmail.com
Tue Jul 15 08:03:51 EDT 2008
On Tue, Jul 15, 2008 at 3:16 AM, Luis Lavena <luislavena at gmail.com> wrote:
> On Mon, Jul 14, 2008 at 12:11 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
>> On Sun, Jul 13, 2008 at 4:50 PM, Charles Grindel <cgrindel at yahoo.com> wrote:
>>> Thanks for the info, Luis. I am glad that they fixed the calling a batch
>>> file issue. I have had to handle this myself in several different
>>> I do have one additional question. It sounds like your setup is very
>>> similar to ours. Is your project new or did you upgrade? Do you run
>>> autospec or autotest from the command line? It seems like running autotest
>>> directly should still work given the history comment, but I could not get
>>> things to fly until I started using autospec. Just curious.
>> When we introduced autospec, we also changed the way rspec identifies
>> itself to autotest such that an ENV var must be present (which is set
>> by autospec) - so no, the autotest command won't work.
> Hmn, really?
> rspec, commit 5bb989c6a54e325198e180ef3d4e59b5bf6eb21c
> rspec-rails: commit 9a1e10e7b71f7e8e4fb910a9695ee69abec63816
Hmm. Well, it's not supposed to work :) We added autospec specifically
so that it wouldn't. Check out
Any reason that shouldn't work on windows?
> But in any case, if you say that I should use script/autospec, then I should :-)
> Luis Lavena
> AREA 17
> Human beings, who are almost unique in having the ability to learn from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-devel