Behat Tests Failing #3968
Comments
|
I was confused initially because without the server running, Behat tests shouldn't pass, but it turns out this is explained by the Behat tests in this particular application accessing the Drupal container directly rather than via web requests (which would probably fail). Clearly something is going wrong during the web server start. We need to get the output from that command to have any hope of troubleshooting this. |
|
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
|
I'm doing some additional debugging on this to try and get some output related to the error. It looks like when I manually do drush runserver, it works. |
|
I downgraded a project to drush 9.7.1 instead of 10.x and suddenly things seem to be working again. i've looked at the diff from 9.7.1 to 10.2 and nothing immediately jumps out at me as different on the RunServer command -- drush-ops/drush@9.7.1...10.2.0 |
|
It appears after comparing across a few projects, that my problem here is actually horribly out of date behat.yml and example.local.yml files in the /tests directory It's unclear at the moment if we failed to provide an update hook, or if I just missed one. But somewhere between Drush 9.6 and 10.x, and BLT 10 and 11, the "old" config "stopped working" for whatever reason. The new config works just fine (facepalm). |
|
Thanks for following up. Do you have any insight as to what specifically in the config was failing? Is there anything BLT could do differently to have made debugging this easier? |
|
I don't know how common it is for people to change these files... However, my behat.yml file was particularly out of date (see Drupal4Gov/Drupal-GovCon-2017@ce5a6ad#diff-17d136558ee3ab9bc09984b5af32821d and Drupal4Gov/Drupal-GovCon-2017@ce5a6ad#diff-1f9e31ef1a0de71ecab91db0af38903c). For me, I re-ran the blt initi config script a few times, and expected "something" to change if I was out of sync (but I had to manually go and update these files). So it might be nice to have some sort of config recipe that would reset these files to "BLT Standard" if nothing else? |
|
I'm having the same issue. Acquia pipelines keep failing for exactly same reason and same error output. I'm on BLT version 13.4, Drupal version 9.4.2 and Drush version 11.0.5. @mikemadison13 Can you please indicate what changes you made manually to make this work? |
|
@alfattal Did you get anyfix for this? I am also seeing similar issue. I'm on BLT version 13.7, Drupal version 9.5.2 and Drush version 11.0.5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This may be related to #1382.
I want to...
Upgrade to BLT 11, Drush 10, etc.
It's not working because...
Behat tests are not executing due to the server not starting. Note that if I go into ci.blt.yml and change the value of
tests.run-serverfrom true to false, then it seems to work fine. I'm not sure why it was ok prior to this update and not post? Maybe a drush thing?Detailed error output
BLT doctor output
System information
The text was updated successfully, but these errors were encountered: