Download the PHP package alorel/phpunit-auto-rerun without Composer
On this page you can find all versions of the php package alorel/phpunit-auto-rerun. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phpunit-auto-rerun
Allows failed PHPUnit tests to automatically rerun.
Use cases
Anywhere where there is an external dependency which you don't have full control of, e.g. when developing an SDK for some API, which might apply rate limiting or experience brief downtime.
Requirements
- Tested on HHVM
- PHP 5.6 or 7.0+
- Tested on PHPUnit 5.4 (
require-dev ^5.0), but might run on older versions (update your installation!)
Installation
Usage
You can integrate retry functionality in your tests in one of two ways: using class inheritance or using traits.
In many situations, you can simply extend your test cases from PHPUnit_Retriable_TestCase, which itself extends the original PHPUnit_Framework_TestCase. Here, all you need to do is replace the class in your test cases:
would become
In situations where your test cases have complex inheritance already, you can just use a trait in the test cases that need retry functionality:
Modifying existing test cases/reverting back
The PHPUnit_Retriable_TestCase class was intentionally left in the global namespace to resemble the original PHPUnit_Framework_TestCase as much as possible.
Most IDEs will generate/suggest a test case template to contain
so you can safely do a tests-wide search-and-replace operation in either direction.
Configuration
Configuration is performed via annotations, same way you'd configure expected exceptions, @befores and so on:
@retryCountspecifies the maximum number of times a test case will run. Setting this to0will simply invoke the original test runner, setting it to1will run a test without retries (equivalent functionality), setting it to5will run it once and retry up to 4 times upon failure.@sleepTimespecifies how many seconds the script will sleep between retries.
Both these values default to 0.
Configuration can be performed by annotating both the class and the test method - class annotations are applied to all methods and are overriden by method annotations, for example, consider the following snippet:
FAQ *
Q: Will this work with
@dataProviderannotations? A: Yes - the test will continue retrying with the same data provider value and continue to the next one when the test succeeds. This applies to both array data providers and generators/iterators.
Q: Why do I end up with a higher number of assertions than before? A: Even when a test fails it still increments the number of assertions made - it was not immediately obvious how to change this and I don't see it as an important feature, therefore I didn't bother implementing it.
Q: Can I set the configuration parameters via CLI/phpunit.xml? A: No and it does not appear to be possible without editing the original PHPUnit code.
* I wrote put these together before release, no one's asked them. Apologies for the ruse. :disappointed:
