Re: [Radiant] Error when testing extensions
Are these new extensions or ones that you started before the official release? Sean On 5/5/07, Andrew O'Brien <[EMAIL PROTECTED]> wrote: > Hi everyone, > > I'm trying to develop some extensions and whenever I try to run a test I get: > > uninitialized constant > ActionController::Assertions::ResponseAssertions (NameError) > > I'm running radiant 0.6 (frozen from the gem). This happens for > everything: unit tests, functional tests, tests run through rake, > tests run directly -- you name it. > > Any ideas? > > Thanks, > Andrew > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
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 might be the problem, I tried to uninstall and re-install but I get the same error. Leon Yeh New Avenue Systems Inc. Sean Cribbs wrote: > Are these new extensions or ones that you started before the official release? > > Sean > > On 5/5/07, Andrew O'Brien <[EMAIL PROTECTED]> wrote: > >> Hi everyone, >> >> I'm trying to develop some extensions and whenever I try to run a test I get: >> >> uninitialized constant >> ActionController::Assertions::ResponseAssertions (NameError) >> >> I'm running radiant 0.6 (frozen from the gem). This happens for >> everything: unit tests, functional tests, tests run through rake, >> tests run directly -- you name it. >> >> Any ideas? >> >> Thanks, >> Andrew >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> >> > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
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 attachment_fu cannot be used in Radiant without some manual requires, but I haven't discovered what exactly breaks in Dependencies code. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
Indeed, I am not sure its a bug or a feature, but extensions can only be tested in application mode. Regards, Erik. Andrew O'Brien wrote: > Hi everyone, > > I'm trying to develop some extensions and whenever I try to run a test I get: > > uninitialized constant > ActionController::Assertions::ResponseAssertions (NameError) > > I'm running radiant 0.6 (frozen from the gem). This happens for > everything: unit tests, functional tests, tests run through rake, > tests run directly -- you name it. > > Any ideas? > > Thanks, > Andrew > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
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 the extension was created before 0.6 was released you may be forced to run the tests in application mode. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
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 vendor directory? -Andrew On 5/6/07, John W. Long <[EMAIL PROTECTED]> wrote: > > 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 the extension was created before 0.6 was released you may be forced > to run the tests in application mode. > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
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"? By "application mode" do you mean that radiant is unpacked in the > vendor directory? Application mode is when you are running Radiant like a normal Rails app (you checked it out via SVN or extracted the Zip or Tar), instance mode is what you get by default when you create a Radiant "project" with the "radiant" command. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Error when testing extensions
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 >> 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 the extension was created before 0.6 was released you may be forced > to run the tests in application mode. > -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
