That set of disruptions is not applied to the testDef, and the tests are silently skipped. When the test execution reaches the point where the disruptions are applied, the disruptions property is not an array (as expected), but a function, and fluid.each(disruption, ...) is a no-op.

The required setup for associating disruptions with testdefs is off in this case, somewhere in SettingsGet.js.