The addition of LightningExtension subcontexts has made it more difficult to toggle Lightning's Behat tests on or off.
Previously, running Lightning's Behat tests required simply telling Behat the file path to the tests. The Drupal extension would discover lightning.behat.inc, and custom step definitions would be recognized.
Now, custom step definitions live in additional places where the Drupal Extension cannot auto-discover them. To run Lightning's Behat tests, one must modify their Behat configuration to manually include the new LightningExtension classes.
At present, this breaks the testing integration with BLT. Maybe I'm missing something?
Comment | File | Size | Author |
---|---|---|---|
#3 | 2836258-3-lightning-extension-autoload.patch | 914 bytes | balsama |
Comments
Comment #2
balsamaComment #3
balsamaWe'll come up with a different approach in 2.0.1. In the interim, you can use this patch which should allow you to target the scenarios with missing definitions using the @lightningextension tag. I only found two scenarios to target:
Marking as needs work since we need a more permanent solution.
Comment #4
geerlingguy CreditAttribution: geerlingguy commentedLinking for more context: Behat test failure with default/OOTB BLT install through GitHub/Acquia Pipelines (from BLT project).
Comment #6
phenaproximaComment #7
phenaproxima