Steve Brazier

I believe Travis does it by setting up small virtual machines for each environment you want to test. It'd be a fairly chunky piece of work to do but would...

I'd be tempted to suggest vagrant (http://www.vagrantup.com/) for this but then we've added a ruby dependency which is possibly counter to the aims of this project.

Well that's definitely worth a look. We could implement a section where you provide phpbrew statements: 5.3.10 +mysql+sqlite+cgi 5.5.1 +mysql+sqlite+cgi etc... and then all of the test plugins get run...

The requirements mention Ubuntu and Debian as well. But it does mean that windows users wouldn't be able to use this. My preference would be that with configuration omitted PHPCI...

And just posting one more tool that might be useful when this gets done: https://github.com/virtphp/virtphp

I'm definitely leaning towards replacing this functionality that kills all of the supervisors children. As this was the original reason for adding this functionality in the first place.

After experimenting with killing all supervisor children it feels like it adds more complexity for very little gain. I'm now in favour of removing the chaotic supervisor all together.

As discussed in slack. I really like this idea. It feels like it should be rarer than a simple process kill. I'd expect it to have it's own config for...

Thanks for reporting 👍 I agree this is an important thing to have

The cucumber route is an interesting one. This project isn't technically a cucumber (it's more "inspired by" than a direct implementation) but it might still might be a route to...