README

Driven is a command line tool for generating a PHP project skeleton that is ready for TDD and DDD(domain driven design).

Directory Structure

Driven will create a directory structure that nicely supports a layered architecture.

├── bin
|   └── doctrine
├── functional
|   └── Driven
├── it
|   └── Driven
|       ├── Infrastructure
|       |   └── Persistence
|       |       └── Doctrine
|       |           ├── Repositories
|       |           ├── DoctrineTest.php
|       |           └── classes.txt
|       ├── datasets
|       └── DbTest.php
├── src
|   └── Driven
|       ├── Domain
|       |   ├── Model
|       |   |   ├── Repository.php
|       |   |   └── Entity.php
|       |   └── Service
|       └── Infrastructure
|           └── Persistence
|               └── Doctrine
|                   ├── Repositories
|                   |   └── RepositoryBase.php
|                   ├── mappings
|                   ├── proxies
|                   ├── ConfigurationFactory.php
|                   ├── EntityManagerFactory.php
|                   ├── UnitOfWork.php
|                   └── doctrine.cfg.json
├── test
|   ├── Driven
|   |   ├── Domain
|   |   |   ├── Model
|   |   |   └── Service
|   |   └── TestBase.php
|   ├── fixtures
|   └── bootstrap.php
├── composer.json
└── phpunit.xml.dist

Where Driven would be replaced with your supplied namespace/vendor dir.

composer.json

Driven comes with a composer.json file that includes the following dependencies: phpunit, phpunit/dbunit, and doctrine/orm. The composer.json file also includes autoloader configurations for all source and test directories.

Testing Classes

TestBase.php

A base test case for unit testing. It contains helpers for loading fixtures from the fixtures directory, and has methods for getting and setting private/protected properties.

DbTest.php

A base test case that extends PHPUnit's Database_TestCase extension. Contains all the behavior available in TestBase.php.

It takes advantage of PDO, and the dsn can be configured on a per test basis by overriding the default dsn:

protected $dsn = "pgsql:host=%s;dbname=%s;user=%s;password=%s";

Additionally you can override the default schema name by overriding the schema property in tests:

protected $schema = ":dbtest:";

By default, driven assumes PostgreSQL. This database supports the TRUNCATES operation for removing rows. The DbTest takes advantage of this. If you use a database that does not support this, then override the $truncates property:

protected $truncates = false;

In addition, there is a helper that can be called to load a dataset from xml into the database using the PHPUnit provided method getDataSet. It will look for these datasets in the datasets directory contained in the integration test suite: it

public function getDataSet()
{
    return $this->dataset('dummy-data.xml');
}

For more information on using the PHPUnit database extension, take a look here.

DoctrineTest.php

This base test case extends DbTest, and takes advantage of some Doctrine2 tools to make testing easier. It makes use of the UnitOfWork to test a typical work flow in a web application. It will create a schema for testing based on the list of supplied classes. Entity classes are supplied via the $classes property.

protected $classes = array('Driven\\Domain\\Model\\Entity\\Entity');

The classes.txt file exists if you prefer to manage that list of classes in a separate file. It follows a format of one class per line, with each line ending in a comma:

Class1,
Class2,
Class3

If the corresponding mapping files exist in the mappings directory, the schema for the given entities will be torn down and created before each test.

Configurations are read from doctrine.cfg.json, so make sure you set the proper environment variable before running PHPUnit.

ENV=development vendor/bin/phpunit it

All test suites and the bootstrap file that loads the composer autoloader are referenced in the phpunit.xml.dist file.

Persistence Classes

All persistence related classes are kept in the Doctrine directory. The components have been tested and used as part of the project located here.

mappings

This directory stores the xml mappings used with doctrine. It comes with a sample file to demonstrate conventions.

proxies

This is where doctrine will look for proxy classes. These should be generated using the doctrine console.

ConfigurationFactory.php

This class is used to generate configurations for doctrine based on the ENV environment variable (development or production).

EntityManagerFactory.php

Used for creating or getting a singleton EntityManager. The workhorse for the packaged UnitOfWork and Repository.

RepositoryBase.php

A handy base for all entity repositories to extend. Includes methods to fetch all entities, fetch a single entity by id, fetch multiple entities by condition, persist an entity, and delete an entity. The only requirement is that subclasses specify the entity type they are persisting:

class MyEntityRepository extends RepositoryBase
{
    protected $type = 'Driven\\Domain\\Model\\MyEntity\\MyEntity';
}

UnitOfWork.php

A unit of work for transactions to take place within. Contains your standard begin, commit, and rollback methods.

doctrine.cfg.json

A json file for configuring credentials for development and production.

Packaged doctrine console

A fully functional doctrine console comes packaged in the bin directory. Some tweaking may be required depending on your OS to make it executable. Nix users can simply do the following chmod +x doctrine.

Usage

Driven will create a project structure inside the current working directory. The only available option is to specify the composer binary. By default composer is assumed to be globally installed as composer.

If you have a composer.phar , you can use it with driven like so:

driven -c "php composer.phar" MyProject

Installation

###Composer### Driven can be installed via composer. Just add the following to your composer.json file:

"require": {
    "brianium/driven": "dev-master"
}

Then run php composer.phar install

You can also clone the repository directly from github.

After installation it may be helpful to setup a symbolic link so you have access to driven globally.

sudo ln -s /path/to/driven/bin/driven /usr/bin/driven

###Build a phar### A phar can be created by running php package.php from the project root. This will create build/driven.phar.

If you receive an error that looks like:

creating archive "build/driven.phar" disabled by INI setting

This can be fixed by setting the following in your php.ini:

; http://php.net/phar.readonly
phar.readonly = Off

brianium / driven

Maintainers

Details