#facile-it/paraunit
Paraunit is a tool for faster executions of PHPUnit test suites. It makes this possible by launching multiple test in parallel with single PHPUnit processes.
Paraunit is developed using Symfony2 components.
Paraunit reads PHPUnit's .xml configuration file, so it's needed to know which test to load.
If you are testing a Symfony2+Doctrine application, it's suggested to use also facile-it/paraunit-testcase, to avoid database concurrency problems during functional testing; also, if your want to run functional tests, remember to warm up the cache before. in order to avoid a mass cache miss with concurrency problems, and subsequent random failures.
To use this package, use composer:
- from CLI:
composer require facile-it/paraunit - or, directly in your
composer.json:
{
"require": {
"facile-it/paraunit": "~0.4"
}
}
Paraunit starts as a Symfony2 console command, but it's provided through a bin launcher; you can run it like this: (assuming your composer's bin dir is vendor/bin)
vendor/bin/paraunit run
This command will launch all the tests in all your configured testsuites.
###Optional parameters
If your phpunit.xml.dist file is not in the default base dir, you can specify it by:
vendor/bin/paraunit run --configuration=relPath/to/phpunit.xml.dist
or with the short version:
vendor/bin/paraunit run -c=relPath/to/phpunit.xml.dist
Also it's possible to provide only a directory, in such case paraunit will look for the 'phpunit.xml.dist':
vendor/bin/paraunit run -c=relPath/to/xml/file/
You can run a single test suite using:
vendor/bin/paraunit run --testsuite=testSuiteName
If you have problem running the tests, or the execution stops before the results are printed out, you can launch paraunit in debug mode, with:
--debug
It will show a verbose output with the full running test queue.
Paraunit prints a parsed result from the single PHPUnit processes. This parsing is a delicate process, and it could sometimes fail; if you are expiriencing any problems, try the --debug option, identify the problematic test, and try running it alone; if it's ok and the parser is at fault, please open an issue here on GitHub with the full single test output.
Anyhow, Paraunit doesn't rely on the parser's results to provide the final exit code; instead, it looks only to the processes' exit codes: it will return a clean zero exit code only if all the PHPUnit processes gave it a zero exit code. So you can safely use it in your CI build ;)