How to follow symlinks when using modman

[robbieaverill]

How to follow symlinks when using modman

[IvanChepurnyi]

Hi Robbie,

What is your directory stucture?

[robbieaverill]

Hi @IvanChepurnyi,

I've got the EcomDev PHPUnit framework installed into my main repository. I use it regularly.

I recently initiated modman and cloned a small repository I've been working from GitHub into the local pool. It now resides in ./modman/my-repo-name/app/code/local/MyVendor/MyPackage/Test. Modman has symlinked it from app/code/local/MyVendor at the MyPackage point to the above (minus the Test).

FYI my example module has a ConfigTest.php test class under MyPackage/Test/Config/ConfigTest.php and a resource model test under Test/Model/......./ColletionTest.php. (Yeah, the phpunit declaration is in my config.xml, although it's under the symlink of MyPackage.)

Here's an example of what works and doesn't:

• phpunit --group MyVendor_MyPackage (no tests found)
• phpunit --list-groups (doesn't list MyVendor_MyPackage)
• phpunit (doesn't run my tests)
• phpunit app/code/local/MyVendor/MyPackage (doesn't run my tests)
• phpunit app/code/local/MyVendor/MyPackage/Test (DOES run my tests)

Edit: you can see a practical example from the Travis build where this is failing here: https://travis-ci.org/robbieaverill/magento-attribute-option-order-fix/builds/90030542.

Hope this helps.

Cheers,
Robbie

[robbieaverill]

Baaaaaaaah.

Somehow the PHPUnit declaration had been lost from my config.xml file. Stupid.

Thanks for your help anyway @IvanChepurnyi!