# Test failures when I have extra admin tabs and the reorder e

**URL:** <https://www.ruby-forum.com/t/test-failures-when-i-have-extra-admin-tabs-and-the-reorder-e/105008>\
**Category:** Radiant CMS\
**Created:** [May 24, 2007, 9:57pm UTC](https://www.ruby-forum.com/t/test-failures-when-i-have-extra-admin-tabs-and-the-reorder-e/105008 "2007-05-24T21:57:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Victor\_Cosby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/e9a140/32.png) [@Victor\_Cosby](https://www.ruby-forum.com/u/Victor_Cosby)\
**Post date:** [May 24, 2007, 9:57pm UTC](https://www.ruby-forum.com/t/test-failures-when-i-have-extra-admin-tabs-and-the-reorder-e/105008/1 "2007-05-24T21:57:15Z")

</div>

I’m hoping someone else has run across the failures below and know how  
they might be addressed before I go much further.

I’ve narrowed the failures down to two extensions I’m using, the  
reorder and assets extensions. The StandardTagsTest fails due to the  
reorder extension being added and the ExtensionInitializationTest  
doesn’t seem to recognize when an extension adds an admin tab.

I suspect there may be a conflict between the core Radiant tests and  
the extensions since everything appears to be working fine in  
development and production environments. And it seems like this kind  
of conflict might be inevitable for some tests if an extension alters  
core behavior, so I’m curious about how folks are avoiding that.

Thanks,  
Victor

1. Failure:  
test\_tag\_children\_each\_attributes(StandardTagsTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/helpers/render\_test\_helper.rb:5:in  
`assert_renders' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/unit/standard_tags_test.rb:34:in`test\_tag\_children\_each\_attributes’]:  
\<"a b c d e f g h i j "\> expected but was \<"j b c d e f g h i a "\>

2. Failure:  
test\_tag\_children\_each\_with\_status\_attribute(StandardTagsTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/helpers/render\_test\_helper.rb:12:in  
`assert_render_match' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/unit/standard_tags_test.rb:43:in`test\_tag\_children\_each\_with\_status\_attribute’]:  
\<"j a b c d e f g h i draft "\> expected to be =~ \</^(draft |)a b c d e  
f g h i j( draft|) $/\>

3. Failure:  
test\_tag\_children\_first\_parameters(StandardTagsTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/helpers/render\_test\_helper.rb:5:in  
`assert_renders' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/unit/standard_tags_test.rb:103:in`test\_tag\_children\_first\_parameters’]:  
\<“a”\> expected but was \<“j”\>

4. Failure:  
test\_tag\_children\_last\_parameters(StandardTagsTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/helpers/render\_test\_helper.rb:5:in  
`assert_renders' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/unit/standard_tags_test.rb:120:in`test\_tag\_children\_last\_parameters’]:  
\<“j”\> expected but was \<“a”\>

5. Failure:  
test\_tag\_parent(StandardTagsTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/helpers/render\_test\_helper.rb:5:in  
`assert_renders' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/unit/standard_tags_test.rb:389:in`test\_tag\_parent’]:  
\<“DocumentationPage With Content Type Set On LayoutAnother Page With  
LayoutGalleryInheritance Test PageSmall TestPage with YAML configTest  
PageNews ArchivesAssorted RootNo CacheArchiveParentPage With  
LayoutRadius Test PageTextile”\> expected but was \<“Another Page With  
LayoutArchiveAssorted RootDocumentationGalleryInheritance Test  
PageNews ArchivesNo CachePage With Content Type Set On LayoutPage With  
LayoutPage with YAML configParentRadius Test PageSmall TestTest  
PageTextile”\>

298 tests, 629 assertions, 5 failures, 0 errors

1. Failure:  
test\_reactivate(ExtensionInitializationTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/functional/extension\_initialization\_test.rb:68:in  
`assert_admin_tabs' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/functional/extension_initialization_test.rb:42:in`test\_reactivate’]:  
\<4\> expected but was  
\<5\>.

2. Failure:  
test\_reloading(ExtensionInitializationTest)  
[/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/functional/extension\_initialization\_test.rb:68:in  
`assert_admin_tabs' /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/test/functional/extension_initialization_test.rb:24:in`test\_reloading’]:  
\<4\> expected but was  
\<5\>.

116 tests, 491 assertions, 2 failures, 0 errors

---

<div class="post-metadata">

**Author:** ![Victor\_Cosby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/e9a140/32.png) [@Victor\_Cosby](https://www.ruby-forum.com/u/Victor_Cosby)\
**Post date:** [May 24, 2007, 10:12pm UTC](https://www.ruby-forum.com/t/test-failures-when-i-have-extra-admin-tabs-and-the-reorder-e/105008/2 "2007-05-24T22:12:17Z")

</div>

On May 24, 2007, at 3:55 PM, Victor Cosby wrote:

> I suspect there may be a conflict between the core Radiant tests and  
> the extensions since everything appears to be working fine in  
> development and production environments. And it seems like this kind  
> of conflict might be inevitable for some tests if an extension alters  
> core behavior, so I’m curious about how folks are avoiding that.

My recently checked in forms extension[1] also causes some Radiant  
tests to fail. In particular, SiteController tests. I put a few  
minutes into it and decided it wasn’t worth the effort at the time. I  
don’t know how to avoid it yet, but I have the feeling that an  
extension shouldn’t cause core tests to stop working. I suppose in  
the end, it is going to require them to know nothing concrete in the  
way of object counts, tab counts, etc.

aiwilliams

[1] [http://dev.radiantcms.org/svn/radiant/trunk/extensions/forms](http://dev.radiantcms.org/svn/radiant/trunk/extensions/forms)