ConfigImportAllTest tries to enable all available modules.

When running the test locally, this also includes whatever contrib modules might be present on the site. Meaning, you don't run what the testbot runs.

The test should limit itself to core modules ?

Comments

yched’s picture

Status: Active » Needs review
StatusFileSize
new805 bytes

patch

yched’s picture

Easy RTBC ?

amateescu’s picture

Status: Needs review » Reviewed & tested by the community

Very easy :)

yched’s picture

jibran’s picture

+++ b/core/modules/config/src/Tests/ConfigImportAllTest.php
@@ -53,7 +53,7 @@ public function testInstallUninstall() {
       // Filter hidden, already enabled modules and modules in the Testing
       // package.

This comment needs update now.

yched’s picture

StatusFileSize
new1000 bytes
new866 bytes

Oops, indeed :-)

Just a comment fix, as the interdiff shows, so keeping at RTBC.

alexpott’s picture

So I'm ambivalent about this change. On one hand it means that modules laying around in your checkout don't influence test results and you run on the same code base as testbot - otoh - we've had this pattern with d7 and d8 for the module install/enable/uninstall/disable test. And if you get failures then it exposes bugs in those modules.

yched’s picture

A test should have a fixed scope as to what it tests ?
It's really weird that some test passes on the testbot and fails locally because of some stuff that happens to lie around on my disk outside the core/ folder ?

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Well the scope in your codebase :) but I'm not that fussed and if it helps so that people won't moan about this test then yay. Committed 3207072 and pushed to 8.0.x. Thanks!

  • alexpott committed 3207072 on 8.0.x
    Issue #2417817 by yched: Keep contrib modules out of ConfigImportAllTest
    

Status: Fixed » Closed (fixed)

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