Allow different features dir

[jricardo27]

Allow to specify an alternative features directory

Useful when for some unfortunate reason there is already a directory called features.

[koterpillar]

Don't do this, releases are independent of pull requests.

[koterpillar]

What's the rationale for this? With this change, the steps cannot be shared between features and that creates confusion.

Remember that you can always run a part of the features by passing features/main or features/alternative to aloe/harvest.

[koterpillar]

If features is an existing module, you can still create, for example, gherkin_tests/features and put the features there.

I think not requiring the features directory be named features is a better approach, but need to think about how to discover steps in that case. Possible solution:

• If it has feature files (and is a module), it is a feature directory.
• Steps are loaded from every feature directory found.

[danni]

I agree, I think in terms of Aloe you would just pass it to the command. However I think there's room for it in Aloe-Django as something to go in your settings file?

[koterpillar]

Need to document what to do if you already have a module called features and you don't want to dump all the features there (solution: put them into gherkin_tests/features or similar).