Introduce "composer test" script

[RobLoach]

Composer scripts allows running commands through composer, along with the updated bin PATHs. We can use this to run the tests through phpzone itself.

For some reason, behat is failing for me. Works on Travis though.

[jakubzapletal]

Thanks for PR! I just wonder why do you want to run this via composer when it could be run directly by bin/phpzone tests?

[RobLoach]

A few reasons:

1. I don't have phpzone installed globally

2. composer test is easier to remember than bin/phpzone tests

3. Simplifies .travis.yml

4. Composer registers bin PATHs for us so composer script ends up being just phpzone tests, again loosing the bin/

5. Ends up being documented when running the composer command....

   show Show information about packages
   status Show a list of locally modified packages
   test Run the test script as defined in composer.json.
   update Updates your dependencies to the latest version according to composer.json, and updates the composer.lock file.

It all comes down to simplification. No real gain here other than that.

[jakubzapletal]

I see your point. It's good idea to have it in composer, but I thin it would be better to have "old" travis or use bin/phpzone tests there because not too much people now feature of scripts in composer and it could be confusing for them. What do you think?

[RobLoach]

not too much people now feature of scripts in composer and it could be confusing for them.

What if, across all PHPZone projects, we were to document it in README.md under a "Development" heading? The only way to teach people is to document and use it.

[jakubzapletal]

I'm not sure if it is a good move. This project was created as a tool to make a development easier and it would be awkward if this project would use Composer for development. I think we should be an example to others how PhpZone could be used.

Thanks to your opinion to be able to run commands without bin/ I am thinking to create PhpZone also as a stand-alone app like Composer so that it could be installed locally or globally and then called simply by phpzone COMMAND. But I am still thinking if it's a good idea and if do this for release 0.2 or let it for 0.3. What is your opinion?

[RobLoach]

@jakubzapletal Agreed... And have it used across all phpzone projects too.