Erik van Oosten wrote:
Indeed, I am not sure its a bug or a feature, but extensions can only be
tested in application mode.
Um, no. That was true for most of the mental branch's life, but it is
not true for the 0.6 series. You can run tests for extensions in
instance or application mode.
If
I did have 0.6RC2 installed, but have upgraded the the stable version. The
extensions (and the radiant instance) were all created after the upgrade.
This may be an obvious question but what's instance mode and application
mode? By application mode do you mean that radiant is unpacked in the
Andrew O'Brien wrote:
I did have 0.6RC2 installed, but have upgraded the the stable version. The
extensions (and the radiant instance) were all created after the upgrade.
Tests run for extensions on 0.6 not RC2.
This may be an obvious question but what's instance mode and application
mode?
Ah, that's good news. I'd better upgrade to the 0.6 release then (I am
still on RC2).
I guess I can recreate my extension, and then copy in all the code.
Regards,
Erik.
John W. Long wrote:
Erik van Oosten wrote:
Indeed, I am not sure its a bug or a feature, but extensions can only be
Hi Sean and Andrew,
I have the same problem. I have created an extension on mental and pre
0.6 release. I try to fix it but can not find the problem. This is only
happen for me when I run the test on instance mode. I have not try to
run this on svn installation. I thought my gem installation
On 5/5/07, Andrew O'Brien [EMAIL PROTECTED] wrote:
uninitialized constant
ActionController::Assertions::ResponseAssertions (NameError)
Radiant - by having its own initializer - somehow messes with Dependencies
and its ability to do autoloading ninja magic. I discovered this when I
realized
