bitwasp/testing-php

This package is abandoned and no longer maintained. No replacement package was suggested.
There is no license information available for the latest version (v0.1.1) of this package.

Composer package which includes most common development & testing software for PHP, and a sample build.xml for phing

Maintainers

Details

github.com/Bit-Wasp/testing-php

Homepage

Source

Issues

Installs: 11 106

Dependents: 6

Suggesters: 0

Security: 0

Stars: 8

Watchers: 3

Forks: 1

Open Issues: 0

v0.1.1 2016-01-05 19:18 UTC

Requires

Unknown License 633bea97c4733ac31508f73595382395de4000f6

This package is not auto-updated.

Last update: 2020-01-24 15:47:18 UTC

README

Composer package for PHP unit testing tools, using Phing for Jenkins or local development Includes:

  • pdepend
  • phpmd
  • phpunit
  • phpcs / phpcbf

Installation:

This package should be installed via composer, which takes care of loading dependencies appropriate for your build.

composer require bitwasp/testing-php

or add it to your composer.json:

    "require": {
        "bitwasp/testing-php": "@stable"
    }
...

Usage:

Build targets can be run by calling: phing <target> Review build.xml for the targets you can run against your code.

Import this build script:

The simplest way to get started is to import this projects build.xml file in your own build.xml. The only thing you need to change here is YOUR-PACKAGE-NAME. The rest of the file simply configures the binary tools directory, which you must change if you keep them somewhere other than the composer default (vendor/bin) The builddir should be kept the same.

<?xml version="1.0" encoding="UTF-8"?>

<project name="YOUR-PACKAGE-NAME" default="build">

    <property name="toolsdir" value="${project.basedir}/vendor/bin"/>
    <property name="builddir" value="${project.basedir}/build/"/>

    <import file="vendor/bitwasp/testing-php/build.xml" />
</project>

Or roll your own:

Refer to the build.xml, or the documentation of the respective tools. You can import the default build.xml and extend it with your own functionality as required, or take whatever interests you.