--no-coverage option to ovewrite config file

[drgomesp]

The default configuration for all my projects is set to generate html code coverage reports.

Is there anyway I can run the phpunit command at a given time and not generate the code coverage reports without having to change the config file?

This would be something like a --no-coverage option.

[whatthejeff]

Unfortunately, this is not something PHPUnit currently supports and @sebastianbergmann has stated previously that he's not interested in adding new arguments/options.

The easiest solution is to maintain a separate configuration file without logging enabled and switch between the two with the --configuration option.

Another option is to disable Xdebug on your system. Tools like phpbrew make enabling/disabling extensions on the fly very simple. Alternatively, you should be able to roll your own solution without too much effort.

[drgomesp]

...and @sebastianbergmann has stated previously that he's not interested in adding new arguments/options.

Are you sure? I was considering making a PR for this.

[whatthejeff]

Yeah, not unless @sebastianbergmann has changed his mind. See #516.

[beporter]

+1

If command line options are intended to override configuration file settings, then it follows that there should be a way to override in both directions. (XML turns a feature on, command line overrides to turn it off.)

Since there isn't a way to merge settings from multiple configuration files (to allow for shared base options), maintaining multiple configuration files for each collection of settings isn't DRY.

[sebastianbergmann]

Once the configuration branch has been merged there will be a way to merge settings from multiple configuration.

[drgomesp]

@sebastianbergmann 👍