Core: Fix QUnit.module.only() regression where some unrelated modules…

… also executed

This fixes a regression introduced in 2.14.0, restoring the behaviour from 2.13 and earlier.

When `QUnit.module.only()` is used, and there is a later sibling module (implicitly disabled
by the "only" filter), with the later module having a nested module inside it, then since
2.14 that nested module would execute as if it was part of the "only" filter.

Fixes #1610.

src/module.js

@@ -10,7 +10,9 @@ import { globalSuite } from "./core";
 const moduleStack = [];
 
 function isParentModuleInQueue() {
-	const modulesInQueue = config.modules.map( module => module.moduleId );
+	const modulesInQueue = config.modules
+		.filter( module => !module.ignored )
+		.map( module => module.moduleId );
 	return moduleStack.some( module => modulesInQueue.includes( module.moduleId ) );
 }
 

test/cli/fixtures/only/module.js

@@ -45,6 +45,14 @@ QUnit.module.only( "module D", function() {
 	} );
 } );
 
+QUnit.module( "module D1", function() {
+	QUnit.module( "module D2", function() {
+		QUnit.test( "test D3", function( assert ) {
+			assert.true( false, "this test should not run" );
+		} );
+	} );
+} );
+
 QUnit.module.only( "module E", function() {
 	QUnit.module( "module F", function() {
 		QUnit.test( "test F", function( assert ) {