Skip to content

Commit

Permalink
Merge pull request #5623 from Jean85/patch-1
Browse files Browse the repository at this point in the history
[DOCUMENTATION] Update tests README
  • Loading branch information
Ocramius authored Jun 22, 2017
2 parents 379acd9 + 1e97cf2 commit af1ea1a
Showing 1 changed file with 21 additions and 4 deletions.
25 changes: 21 additions & 4 deletions tests/README.markdown
Original file line number Diff line number Diff line change
@@ -1,8 +1,25 @@
# Running the Doctrine 2 Testsuite

## Setting up a PHPUnit Configuration XML
To execute the Doctrine2 testsuite, you just need to execute this simple steps:

..
* Clone the project from GitHub
* Enter the Doctrine2 folder
* Install the dependencies
* Execute the tests

All this is (normally) done with:

git clone [email protected]:doctrine/doctrine2.git
cd doctrine2
composer install
./vendor/bin/phpunit

## Pre-requisites
Doctrine2 works on many database vendors; the tests can detect the presence of installed vendors, but you need at least one of those; the easier to install is SQLite.

If you're using Debian, or a Debian-derivate Linux distribution (like Ubuntu), you can install SQLite with:

sudo apt-get install sqlite

## Testing Lock-Support

Expand All @@ -14,12 +31,12 @@ Install Gearman with PHP as follows:
3. Start it up "gearmand -vvvv"
4. Install pecl/gearman by calling "gearman-beta"

You can then go into tests/ and start up two workers:
You can then go into `tests/` and start up two workers:

php Doctrine/Tests/ORM/Functional/Locking/LockAgentWorker.php

Then run the locking test-suite:

phpunit --configuration <myconfig.xml> Doctrine/Tests/ORM/Functional/Locking/GearmanLockTest.php

This can run considerable time, because it is using sleep() to test for the timing ranges of locks.
This can run considerable time, because it is using sleep() to test for the timing ranges of locks.

0 comments on commit af1ea1a

Please sign in to comment.