[zeta] Re: Fixing and running tests, Travis-CI

On Mon, May 21, 2012 at 12:25 PM, Fabrice PICCINALI
<f.piccinali[@]fazae.com>wrote:

>
> Hello,
>
> is there a wiki where i could cut-and-paste your useful process ?
>

Maybe we should add a wiki on the main repository?
https://github.com/zetacomponents/zeta

That one will probably contain a version of all the (stable?) components.

>
>
> On 21/05/2012 12:07, Benjamin Eberlei wrote:
>
> Hello,
>
> here is a how-to fixing and running the tests for any Zeta Component:
>
> 1. Check out the code "git clone git[@]github.com:zetacomponents/<name>.git"
>
> 2. Get Composer to install dependencies (wget
> http://getcomposer.org/composer.phar) - Put it in $PATH and make
> executable.
>
> 3. Call "composer install --dev" in the root directory of the component.
> At the moment this will install "Base" and "UnitTest" as dependencies into
> the "vendor" directory.
>
> 3a.) If your component is a Tiein you have to add the additional
> dependencies to composer.json file into the "require" key.
>
> 4. Call "phpunit" without any arguments. The phpunit.xml.dist is build
> such that the tests run automatically.
>
> 5. Fix all the errors/failures/problems until the tests are running and
> commit all the changes.
>
> 6. Add ".travis.yml" file into root directory and commit+push. Copy
> contents from
> https://github.com/zetacomponents/Archive/blob/master/.travis.yml
>
> 7. Register on Travis-CI. View your profile and copy the "API Token". Open
> up Admin Page for the component on Github, then Service Hooks. Add your
> username + token in the travis service, don't forget to check "Active".
>
> 8. Test the hook to trigger a build process on Travis CI (see
> www.travis-ci.org main page, project should pop up on top of current list)
>
> I already enabled "Archive" component for testing this process.
>
> If you need any help with the process please ping me on IRC (or mail here)
>
> greetings,
> Benjamin
>
>
Received on Mon May 21 2012 - 11:41:35 BST