On Wed, Jun 25, 2008 at 2:26 PM, Chris Parrish
<[EMAIL PROTECTED]> wrote:
> Use "rake spec:extensions EXT=your_extension_name" to just run the specs for
> your extension.
It had the same results:
http://pastie.org/222128
> By the way, does anyone else think it would be useful to run specific
>
Alex Wayne wrote:
Thats quite odd. Are you sure you are running the latest rspec gem?
Try a
gem install rspec
-Alex
http://beautifulpixel.com
I've had troubles using the rSpec gem because Radiant ships with its own
version of rSpec and rSpec on Rails. Whenever I tried to use the gem,
rS
Acording to http://rspec.rubyforge.org/rdoc/classes/Spec/Rake/SpecTask.html
you can do that
rake spec SPEC=path/to/file_spec.rb
It works like a charm.
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 1:26 PM, Chris Parrish wrote:
Use "rake spec:extensions EXT=your_extension_name" to jus
Chris Parrish wrote:
Use "rake spec:extensions EXT=your_extension_name" to just run the
specs for your extension.
Oh, and you run it from the project's root - not the extension's.
-Chris
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search
Thats quite odd. Are you sure you are running the latest rspec gem?
Try a
gem install rspec
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 12:24 PM, Marty Haught wrote:
On Tue, Jun 24, 2008 at 9:15 PM, Alex Wayne
<[EMAIL PROTECTED]> wrote:
Radiant 0.6.7 generates extensions with a
Use "rake spec:extensions EXT=your_extension_name" to just run the specs
for your extension.
By the way, does anyone else think it would be useful to run specific
spec(s) within an extension?
Perhaps using syntax like:
rake spec:extensions EXT=your_extension_name
FILE=app/controllers/my_c
On Tue, Jun 24, 2008 at 9:15 PM, Alex Wayne <[EMAIL PROTECTED]> wrote:
> Radiant 0.6.7 generates extensions with a spec directory by default, and no
> test directory at all. Its all hooked up already for ya.
Hi Alex,
Yes, I see that but I've run into problems just getting them to run.
So I have a
