[Epic] Request For Contributors - V2.0

[liuggio]

The version 1 has been released and it's time to move on,
in this era laptops have 8 cores and the serial commands execution
is a waste of time, when we wrote the lib the processors number were 4 and now are doubled.

On the events branch https://github.com/liuggio/fastest/tree/events (sorry I didn't change the Readme yet) there's a prototype of the new fastest,
it has been totally rewritten with events approach.

The goals:

• provide a better output decoupled from the processes execution
• provide a better integration for Phpunit/PhpSpec/Behat and third party service
• agnostic parallel processing

The future
In the future it could be also a library to help other applications eg. php-cs-fixer or assetic to parallelize processes.

Now

The great benefit of this new approach is the possibility to fetch the data from each process on runtime, and is possible to recreate the same output of any third party.
Is now possible to print on screen with a simple/ugly Subscriber that waits for events with partial content.

Todo:

In this new branch the todo-list is quite big we have to re-add the PhpUnit and Behat adapters, would be great to do it with a deep integration eg. use the PHPUnit php code to read the folder.

• 1 PHPUnit
  • 1.a InputProducer: Should place the tests into the queue.
  • 1.b PHPUnitOutputSubscriber: handle the output as Phpunit does
  • minor - 1.c Coverage
• 2 Behat Adaptor
• 3 porting of the old UI to the new StdOutUISubscriber
• 4 re-add the MongoDB and Doctrine adapters
• 5 Better windows support [ProcessorCounter] Windows support #1, Forward PATH to child processes #24

Any suggestions or idea are really welcome...

/cc
@giorrrgio @EmanueleMinotto @perk11 @binarious @GrahamCampbell @dpmancus @aitboudad @diegosainz

[giorrrgio]

I would add a better aggregation of errors, so that the tests output is more uniform: e.g. parse the errors and replace the fragmented error output in a single stream of errors parsed from all the processed outputs, with aggregated failure counts. I would add support for skipped and incomplete tests too in the output, so it's easier to remember that you have to face them sometimes.

[liuggio]

@giorrrgio this is a great idea, so you mean to create a Subscriber that emulates the phpunit output?

[giorrrgio]

@liuggio yes, or we can add a generic TestFrameworkUIOutputSubscriber (ok with a better name maybe :P) with a strategy on different test frameworks to provide proper test output aggregation.

[liuggio]

or we can add a generic TestFrameworkUIOutputSubscriber

👍
maybe it can listen also for events like PendingTestEvent or FailedTestEvent

with a strategy on different

instead of a strategy a middlewareSubscriber that intercepts events understand the output (or xml) and raise a PendingTestEvent?

great idea 👍

[liuggio]

with @EmanueleMinotto and @giorrrgio we created https://github.com/liuggio/spawn
This project will extends spawn in order to provide faster tests ops fastest :)