PHPackages                             jdwil/unify - 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. jdwil/unify

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

jdwil/unify
===========

0.0.1(8y ago)3141GPLv3PHP

Since Jul 8Pushed 8y ago1 watchersCompare

[ Source](https://github.com/jdwil/unify)[ Packagist](https://packagist.org/packages/jdwil/unify)[ RSS](/packages/jdwil-unify/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependencies (11)Versions (4)Used By (1)

Unify
=====

[](#unify)

#### What's this thing?

[](#whats-this-thing)

Unify is a tool meant to make your life easier. It allows you to write tests and documentation at the same time, greatly reducing the time and effort spent delivering software. Unify makes a great complement to BDD processes and tools, like Behat. Behat is a fantastic way to document your system with regression testing. Unify aims to fill a similar niche, but on the unit and integration testing side, with a more developer-centric bent.

Example
-------

[](#example)

Below is an actual test. While intentionally simple, when Unify is run on its own project documentation, it will evaluate the code block below and assert that $x does, in fact, equal 'Zm9v'.

```