Download the PHP package testo/fiber without Composer
On this page you can find all versions of the php package testo/fiber. 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 fiber
Fiber / coroutine plugin
[!IMPORTANT]
🪞 This is a read-only mirror.
Active development of the Testo project lives in php-testo/testo under
plugin/fiber/. This repository is automatically synchronized from there on every release.File issues and pull requests in the main monorepo, not here.
About
Runs tests as plain PHP fibers driven by Testo's own cooperative scheduler, so a test (or the code it exercises) may suspend with \Fiber::suspend() and be resumed, and a case's tests may be interleaved to shake out order-dependent races.
#[RunInFiber]— run a test (method) or a whole case (class) inside fibers, scheduled bySchedule::Solo(default),RoundRobinorRandom.Coroutine::spawn()/->await()/Coroutine::concurrently()— add coroutines to the running test's schedule and wait for them; they interleave with the test body (and, under a class-level#[RunInFiber], with the case's other tests) at every suspension point.
The scope is structured: the test is not finished until every coroutine it spawned is. Coroutine failures always surface wrapped in a CompositeException — even a single one; if the test body fails, pending coroutines are cancelled with a CancelledException thrown into them, and an await cycle is broken with a DeadlockException at the guilty await().
Switching is cooperative and happens only at suspension points — there is no event loop and no preemption. This is for fiber-based/cooperative code and race hunting, not for real async I/O: awaiting a timer, socket or Future needs the Revolt event loop — use the testo/bridge-revolt #[RunInRevolt] attribute for that.
Everything lives under the Testo\Fiber\ namespace.
Install
