PHPackages                             bitwasp/testing-php - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Testing & Quality](/categories/testing)
4. /
5. bitwasp/testing-php

AbandonedArchivedLibrary[Testing & Quality](/categories/testing)

bitwasp/testing-php
===================

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

v0.1.1(10y ago)911.4k24PHP >=5.4.0

Since Apr 19Pushed 10y ago3 watchersCompare

[ Source](https://github.com/Bit-Wasp/testing-php)[ Packagist](https://packagist.org/packages/bitwasp/testing-php)[ Docs](https://github.com/Bit-Wasp/testing-php)[ RSS](/packages/bitwasp-testing-php/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (3)Versions (6)Used By (4)

testing-php
-----------

[](#testing-php)

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

- pdepend
- phpmd
- phpunit
- phpcs / phpcbf

#### Installation:

[](#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:

[](#usage)

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

#### Import this build script:

[](#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.

```

```

#### Or roll your own:

[](#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.

###  Health Score

32

—

LowBetter than 72% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity30

Limited adoption so far

Community16

Small or concentrated contributor base

Maturity52

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~65 days

Total

5

Last Release

3786d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/763cdc5cc50414bacd4ff1080eede79432f7c3cc26a3d8aa9031b1537a8bd734?d=identicon)[thomaskerin](/maintainers/thomaskerin)

---

Top Contributors

[![afk11](https://avatars.githubusercontent.com/u/5617245?v=4)](https://github.com/afk11 "afk11 (12 commits)")

### Embed Badge

![Health badge](/badges/bitwasp-testing-php/health.svg)

```
[![Health](https://phpackages.com/badges/bitwasp-testing-php/health.svg)](https://phpackages.com/packages/bitwasp-testing-php)
```

###  Alternatives

[youwe/testing-suite

Contains Youwe's default testing packages for php.

13176.9k8](/packages/youwe-testing-suite)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)