The tests of the 7.x-2.x-dev branch are failing right now. Looks like something in the commits on Mar 23rd to the 2.8 release caused this, even though each of the committed issues individually passed testing.

Initial error is:

Fatal error: Call to undefined function taxonomy_features_api() in /var/www/docroot/sites/all/modules/features/tests/features.test on line 212

If I add a specific

module_load_include('inc', 'features', "includes/features.taxonomy");

then the new error is:

Fatal error: Class name must be a valid object or a string in /var/www/docroot/includes/common.inc on line 7999

CommentFileSizeAuthor
#7 features_tests_failing-2694349-7.patch422 bytesmpotter

Comments

mpotter created an issue. See original summary.

mpotter’s picture

This is odd. I can reproduce the same errors when running tests locally. But even reverting the Features code to v2.7 doesn't help. Very perplexed unless it's something that changed in a recent core update?

mpotter’s picture

Issue summary: View changes

Well, went back to Drupal 7.41 and Features 2.7 and tests still fail. Not sure what's going on here.

mpotter’s picture

Oh, fascinating. Well, problem #1 is that I didn't have "strongarm" downloaded on my local test site, so it wasn't able to install the feature_test module because dependencies were not met. At least I'm past the basic errors now and can test more.

mpotter’s picture

So now locally all Features tests are passing on the 7.x-2.x branch.

Is maybe the testbot broken?

mpotter’s picture

Ah ha!

According to drumm in IRC, this was committed recently #2651854: Only look for dependencies for releases with specific project node types

Features was not using the test_dependencies[] in the info file, so it wasn't loading strongarm, views, etc.

mpotter’s picture

StatusFileSize
new422 bytes

  • mpotter committed ce9da9e on 7.x-2.x
    Issue #2694349 by mpotter: Tests failing for 7.x-2.x-dev branch
    
mpotter’s picture

Status: Active » Fixed

Yep, this fixed the testbot. Woot!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.