The problem was that we were expanding properties in example.local.yml, and have been since at least BLT 11. This wasn't a problem in 11 though because the file already existed in the project template and generally wasn't overwritten.
In fixing this, it became clear that the whole architecture needed some TLC, and we needed to finish getting it out of BLT core.
Part of this re-architecture is to clarify the two Behat "init" or setup commands:
recipes:behat:init: intended to be run once at the start of a project to install a set of template behat scripts and settings
tests:behat:init (nee setup:behat): intended to be run with every Behat invocation to (re)generate Behat local.yml
To be released in conjunction with https://github.com/acquia/blt/pull/4305
Fixes #6
The problem was that we were expanding properties in example.local.yml, and have been since at least BLT 11. This wasn't a problem in 11 though because the file already existed in the project template and generally wasn't overwritten.
In fixing this, it became clear that the whole architecture needed some TLC, and we needed to finish getting it out of BLT core.
Part of this re-architecture is to clarify the two Behat "init" or setup commands:
recipes:behat:init
: intended to be run once at the start of a project to install a set of template behat scripts and settingstests:behat:init
(neesetup:behat
): intended to be run with every Behat invocation to (re)generate Behat local.yml