Summary
The stock tests/behat/bootstrap/FeatureContext.php enables most of drevops/behat-steps but omits five traits that ship in the version the template already requires. Downstream Vortex sites re-add them one at a time.
Two of the five are hard to justify omitting: the template installs the redirect module by default and ships an xmlsitemap.feature, yet neither RedirectTrait nor XmlTrait is wired in.
Details
Add to FeatureContext:
DrevOps\BehatSteps\Drupal\CacheTraitDrevOps\BehatSteps\Drupal\RedirectTraitDrevOps\BehatSteps\IframeTraitDrevOps\BehatSteps\ResponsiveTraitDrevOps\BehatSteps\XmlTrait
No new dependency - all five are already in vendor/ through the existing requirement.
Also decide in the same pass: RestTrait and JsonTrait ship in the same package and are likewise unwired. Three downstream sites pulled in a third-party REST extension for API testing, which suggests the first-party traits would have covered the need had they been enabled. Check whether they do before anyone else reaches for a dependency.
Points to settle:
- Each newly wired trait adds steps that may need a matching feature file so the template's own suite exercises them.
- Some traits carry
@BeforeScenario/@AfterScenario hooks or expect specific modules to be enabled. Confirm none of them break a build where the relevant module is not selected in the installer, and fence the trait if it does.
Summary
The stock
tests/behat/bootstrap/FeatureContext.phpenables most ofdrevops/behat-stepsbut omits five traits that ship in the version the template already requires. Downstream Vortex sites re-add them one at a time.Two of the five are hard to justify omitting: the template installs the
redirectmodule by default and ships anxmlsitemap.feature, yet neitherRedirectTraitnorXmlTraitis wired in.Details
Add to
FeatureContext:DrevOps\BehatSteps\Drupal\CacheTraitDrevOps\BehatSteps\Drupal\RedirectTraitDrevOps\BehatSteps\IframeTraitDrevOps\BehatSteps\ResponsiveTraitDrevOps\BehatSteps\XmlTraitNo new dependency - all five are already in
vendor/through the existing requirement.Also decide in the same pass:
RestTraitandJsonTraitship in the same package and are likewise unwired. Three downstream sites pulled in a third-party REST extension for API testing, which suggests the first-party traits would have covered the need had they been enabled. Check whether they do before anyone else reaches for a dependency.Points to settle:
@BeforeScenario/@AfterScenariohooks or expect specific modules to be enabled. Confirm none of them break a build where the relevant module is not selected in the installer, and fence the trait if it does.