>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #911354. --> Reported by: [yhahn](https://www.drupal.org/user/264833) >>> <p>When using an install profile that is packaged as a distribution (ie. its projects live in <code>profiles/[name]/modules</code>) tests in any modules therein cannot be run successfully. To reproduce:</p> <ol> <li>Install D7 using the standard install profile</li> <li>Create a modules directory at <code>profiles/standard/modules</code></li> <li>Move one of the core modules (e.g. poll) from <code>modules/poll</code> to <code>profiles/standard/modules/poll</code> and then clear your caches.</li> <li>Run poll tests and watch #fail</li> </ol> <p>While the scenario above is obviously unrealistic, downloading an install profile from Drupal.org that contains, say, <code>views</code> in <code>profiles/[name]/modules</code> is a very real case.</p> <h3>Problem</h3> <p>The problem is caused by the module whose test is to be run not being available in <code>drupal_system_listing()</code> given that it lives in a profile directory:</p> <ol> <li>Views is in <code>profiles/[name]/modules/views</code>,</li> <li>When Views' tests are run, the install profile used is <code>standard</code>, leading to the following paths scanned by <code>drupal_system_listing()</code>: <ul> <li><code>profiles/standard/modules</code></li> <li><code>sites/all/modules</code></li> <li><code>sites/[x]/modules</code></li> </ul> </li> <li>Views is obviously not in any of these directories and so the test fails as it cannot enable Views from the get go.</li> </ol> <h3>Approaches</h3> <p>Some possible approaches,</p> <ol> <li>Treat this as a UI problem. Don't show <strong>any</strong> tests for modules in <code>profiles/[name]/modules</code>. Install profiles and distros would not be able to run tests for any of their modules.</li> <li>Always have <code>$test-&amp;gt;profile</code> use the current install profile if the installed profile is not one of the Drupal core install profiles. Tests will likely take much longer to run, especially when they could just be using the lighter <code>testing</code> profile.</li> <li>Adjust <code>drupal_system_listing()</code> to use not only <code>drupal_get_profile()</code> but the 'parent' install profile (the install profile of the site that the test is running on).</li> </ol> > Related issue: [Issue #1242448](https://www.drupal.org/node/1242448)