cameronandwilding / cwtest_behat Goto Github PK

Running the https://github.com/cameronandwilding/CWTest_Behat/blob/master/bin/cwtest-bootstrap.sh script fails if it runs outside of its directory. To make it flexible it shouldn't depend on the caller path.

Currently screenshot folder is not created properly when the parent folder doesn't exist which generates the following warning:

    And I press the Create Blank Edition button                                              # CWTest\Context\SkeletonGeneratorContext::iPressTheCreateBlankEditionButton()
    │
    ╳  Warning: mkdir(): No such file or directory in /Sites/drupal/sites/all/tests/functional/cwtest_behat/vendor/cw/behat_test/src/Context/HelperContext.php line 169

I think the solution would be to create the folder recursively.

Sample folder which failed: cwtest_behat/Behat/../Results/Behat/screenshots/Articlepage.

Perhaps the README file should list the minimum software requirements, or at least some versions of the software this has been successfully tested with.

For example, I had to upgrade Java to 1.8. This is mentioned as a possibility in the troubleshooting section but would have been good if this was obvious from the start.

Hi,

I saw a presentation on this at DrupalCamp London and I've been meaning to try it out ever since! Thanks for all your hard work.

I'm trying to write my first test and I'm not sure where to put my custom contexts and features. I found this video which shows a run-behat.sh that copies files from the Behat_Test_Files directory... but there's no hint of that in this repo (or I'm blind!).

What's the recommended approach here?

Thanks

Currently behat and drupal driver are installed as part of the post installation script. Consider moving these to the dependencies section of compose.json.

Currently bin/stop_selenium_server.sh script is requesting the following URL to shutdown Selenium server:

cURL http://localhost:4444/selenium-server/driver/?cmd=shutDownSeleniumServer

In Selenium 3, such URL is deprecated and does not exist.

As per: shutDownSeleniumServer return 404 after upgrade from Selenium 2 to 3 (beta4)

Related: Cannot shutdown the selenium stand alone server by sending 'shutDownSeleniumServer' command

It's not a big deal, but this is something to be aware when running Selenium in a standalone mode.

The workaround would be to run Selenium server with a role and request LifecycleServlet URI at /lifecycle-manager/LifecycleServlet?action=shutdown. Or just to downgrade to Selenium 2.

I'm not sure what would be the right solution for this, apart of removing mentioned curl request. I'll try to open the PR if I find the right approach.