Conversation
Behat is configured to use the laravel-behat extension and my slightly different (but IMO useful) way of laying out the test folder structure has been done.
… contents of the file but we *do* care that it exists hence it has been committed with the prior commit.
|
Worth pointing out that I added a dummy test to the setup so that it's possible to see vaguely how things work. Once actual tests exist then it'll be deleted I imagine. |
|
I do not understand most of this, but the bits I do don't seem to conflict with the main system. I'm happy to merge, but would appreciate a second opinion |
|
Seems this covers (at least paritally) issue #12 ? I'm happy to go through what I've done if you want to point out sticking areas. For the most part this is just integration of the standard behat stuff with the extra laracasts laravel components bolted in. The only thing thats different from normal IIRC is the way I've organised the test files (which I've done like this to keep things IMO a little easier to parse). |
… a testing setup.
|
all looks good to me and covers whats needed to start with |
Behat is configured to use the laravel-behat extension and my slightly different (but IMO useful) way of laying out the test folder structure has been done.
Essentially each context file is mostly empty and all test definitions are broken out into related functionality traits.
I've also taken the liberty of binding the app/HMS folder to the HMS\ namespace (since I have some behat code that lives there)