Remove --testdox
parameter from phpunit command
#63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Issue
The test output from
ddev phpunit
has the following problems:How does this happen?
Currently the
phpunit
command from this package calls phpunit with a--testdox
parameter.This parameter replaces the printer we previously set with
--printer
.How This PR Solves The Issue
By removing the
--testdox
argument, we fall back to the Drupal output printer.A developer can still manually append
--testdox
by runningddev phpunit --testdox
, if they prefer that format.Manual Testing Instructions
In a project with the ddev-drupal-contrib extension, create a test case like this:
Optionally, add a Drupal web test (e.g. FunctionalJavascript) with a failed assertion.
Run
ddev phpunit
.Expected:
Actual:
Automated Testing Overview
Not yet. I first want to see what fails by doing this change..
Related Issue Link(s)
Interesting post: #29 (comment)
Release/Deployment Notes