Jump to:

23453 Posts in 18902 Topics by 2877 members

General Questions

SilverStripe Forums » General Questions » behat testing setup

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Page: 1
Go to End
Author Topic: 828 Views
  • BlueO
    Community Member
    52 Posts

    behat testing setup Link to this post

    I've been playing around with the behat testing module from here with reasonable success. I'm not too bad with SS but a total newbie when it comes to testing - but I'm aware its the "right thing" to do so I'm keen to figure it out!

    I've got it generally up and running - test db creates just fine, successfully collects to selenium and runs features that use the 'out of the box' definitions work perfectly.

    However, now I want to write my own definitions and I'm really struggling to get behat to recognise my custom featurecontext file. I'm using the behat.yml from the installer (in the root next to framework etc) with these additions:

    features: mysite/tests/behat
    bootstrap: mysite/tests/behat/features/bootstrap
    class: TestFeatureContext

    # Adjust "base_url" to your own website URL.
    # Can be set via environment variables or _ss_environment.php/$_FILE_TO_URL_MAPPING as well.
    #base_url: http://localhost:8888/piemrak/

    # TODO Dynamically set through LocatorProcessor
    files_path: %behat.paths.base%/framework/tests/behat/features/files/
    default_session: selenium2
    javascript_session: selenium2
    goutte: ~
    browser: chrome

    SilverStripe\BehatExtension\Extension ~

    But the TestFeatureContext.php which lives in mysite/tests/behat/features/bootstrap/ fails to load and I get:

    Context class "TestFeatureContext" not found and can not be instantiated.

    on running

    vendor/bin/behat mysite/tests/behat/features/home.feature

    The TestFeatureContext file is taken from the example on github - a class that extends SilverStripeContext.

    So if you got through the lengthy post I'd appreciate some pointers as to where i'm going wrong!


  • dead_salt
    Community Member
    2 Posts

    Re: behat testing setup Link to this post

    Hey Bernard,
    I was having the same problem and it was driving me crazy but then my colleague pointed out that I needed to put a _config.php file in the features folder. Solved the issue all together. Give a try and see if it helps you!

  • BlueO
    Community Member
    52 Posts

    Re: behat testing setup Link to this post

    Hey cheers for that but unfortunately it doesn't seem to help.
    some progress... I ran

    vendor/bin/behat --init

    and it successfully created a FeatureContext.php file for me. However when I run behat after putting a definition in that file it doesn't seem to recognise it - its as though the file isn't loaded at all. Hmm will keep plugging at it.

  • BlueO
    Community Member
    52 Posts

    Re: behat testing setup Link to this post

    OK, so after some investigation I've solved this

    Probably those using this module have more experience with composer/testing that I do so the docs on github skip this point as it is a simple little thing...

    The behat extension uses the composer autoloader to bootstrap the files and this can't be configured through the behat.yml file, instead you do it in composer.json autoload section like so:

    "autoload": {
    "classmap": ["mysite/tests/behat/"]

    with the path being the location of the files you want auto-loaded like your FeatureContext.php
    I figured it out from looking at composer.json and the test files in the CMS and framework dirs so they've got some good examples.

    So now its up in action - its pretty fun to watch selenium run through the tests like magic

Page: 1
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.