1. Ok. The vendor folder change seems kinda reasonable, but I am not as happy with losing the error message if none is found. If they’ve installed the package with git clone then there will never be a vendor folder, and it will just cd ../ all the way up to / without finding anything. Think thats more or less of an issue than allowing composer installed project components to work without having their own dependencies installed? 

You’ve already pointed out that dev packages for a component are not installed for a project, so if they are missing surely the tests will not work correctly? 

2. Call it test/ if you like. We have used tests/ elsewhere but its not a big deal. We’ll standardize on one eventually. :)

-- 
Phil Sturgeon

On April 25, 2014 at 4:17:48 PM, Tom Anderson (notifications@github.com) wrote:

In tests/Bootstrap.php:

> @@ -1,5 +1,43 @@
>  <?php
>   
> -if ( ! @include_once __DIR__ . '/../vendor/autoload.php') {
Because it allows you to run unit tests when the library is installed as part of composer.

Oftentimes I debug libraries while they are installed in composer by composing them but you want access to the whole vendor library you're running in and that's what this bootstrap does. I actually simplified the zfcampus bootstrap by a lot to put this here. https://github.com/zfcampus/zf-apigility/blob/master/test/Bootstrap.php

You'l also see the latest trend in PHP, as zfcampus is controlled by MWOP, that the unit test dir is test and not tests

—
Reply to this email directly or view it on GitHub.