Provide an option to specify command with #7
Conversation
|
+100 Nice feature! I like it and I need :) |
|
Don't merge the PR just yet... I discovered the custom reporter guard uses is incompatible between versions. I have a fix coming soon. |
|
Great work! |
|
@Maher4Ever @jamescarr Awesome! Really looking forward to seeing this in guard-phpunit. |
|
👍 |
|
cool! |
|
Hope this gets merged soon! Since I have to run an old version of phpunit (3.5 does not have all the command line options guard-phpunit uses by default) I haven't been able to use guard-phpunit. With this change I should be able to! |
|
@Maher4Ever could you please merge this? |
|
@jamescarr Is there anything you want to change in this pull request? Or can it be merged in it's current state? @Maher4Ever Could you merge this? There seems to be a lot of interest in this fix. |
|
I think we should use another Repository for Guard-phpunit. |
|
I agree |
|
@MPV The problem I ran into is that the reporter that guard-phpunit uses is incompatible with later phpunit releases. Otherwise it seemed to work fine. |
|
+1 I uses composer as well (as everyone really should at this point). This is needed, as phpunit is no longer in the system path. |
|
I need this as well. |
|
Is there any fork that became an official fork of guard-phpunit ? This one does not seem maintained anymore. |
|
+1, please merge :-) |
|
@adri - there is a fork that I made, that supports this. It's not released yet as the automatic tests do not pass, but it seems to be working ok. Check : https://github.com/marekkalnik/guard-phpunit2 if you're interested |
|
+1 |
12 participants
Since phpunit started publishing packages over composer I've switched to using this method of running phpunit rather than installing globally via pear.
This change defaults to the globally installed phpunit but allows the user to specify an alternative command to run.