PHPUnit execution fails due to ""docker.exe": executable file not found in %PATH%"

[shochdoerfer]

Is there an existing issue for this?

• I have searched the existing issues

Are you sure that this bug is related to this DDEV Integration Plugin?

• I am sure

Enter your error report ID (If available)

No response

Describe the bug

This may or may not be similar to #152.

I have 2 DDEV projects, pretty similar setups. The minor difference is that a different database is used. In one project, the PHPUnit integration works out of the box, thanks to the defaults configured by this plugin. In the other project, I got the following error when I try to execute PHPUnit:

exec: "docker.exe": executable file not found in %PATH%
Current PATH : 

The issue seems to be that PHPStorm can't find the PHP installation in the CLI interpreter configured by DDEV. When trying to find the interpreter PHPStorm returns an error "Failed to parse validation script output"

The same also happens for a colleague when cloning the repo. We don't share the .idea directory via Git, so both installations on 2 different laptops behave exactly the same.

Interestingly I was able to manually fix this problem this morning by adding another CLI interpreter with the exact same settings as defined by the DDEV one. Once I assigned that manually added CLI interpreter to the PHPUnit configuration, it executed just fine.

I compared both .idea directories of the project with a working DDEV setup and the project where it did not work. And the only difference I could spot was a missing <component name="PhpInterpretersPhpInfoCache"> element in the php.xml configuration. When I copied that part into the project that was not working, PHPStorm at least did not show me an error in the UI, but still, I could not execute PHPUnit.

Most likely, this seems to be a regression or a bug in PHPStorm. Not sure if this plugin can do something about it.

Steps to reproduce

No response

Additional context

No response

[shochdoerfer]

I forgot to mention: On the first try, I deleted all the DDEV resources that got created automatically. But that did not help either.

[mwaltonen]

I'm having the same issue here. In php.xml, if I update

<envs pass-parent-envs="false">
  <env name="COMPOSE_PROJECT_NAME" value="ddev-test-project" />
</envs>

to

<envs>
  <env name="COMPOSE_PROJECT_NAME" value="ddev-test-project" />
</envs>

everything works as before. This appears to correspond to placing a check next to "Include system environment variables" when you expand the "Environment variables" field in the "CLI Interpreters" settings.

[ultimike]

I'm having a similar issue and while checking the "Include system environment variables" box does change the error for me, it doesn't solve the issue.

After checking the box, when I attempt to validate my phpcs settings, I get a "Could not open input file: /var/www/html/vendor/bin/phpcs" error message.

-mike

[shochdoerfer]

@ultimike have you tested creating another CLI interpreter configuration with the exact same settings as defined by the DDEV one? Once I did that and assigned that CLI interpreter to the PHPUnit configuration, it worked fine for me.

[rfay]

If you want to come over to Discord we can schedule some live debugging and see if we can sort this out.

[mwaltonen]

Did you click the little spinning wheel icon to detect your php version after checking the box?

[ultimike]

@rfay Thanks, for the offer - I might take you up on this depending on what you think about what I found (keep reading).

@mwaltonen I think you're referring to the "Reload phpinfo" button on the "PHP | CLI interpreter" settings page, correct? If so, yes, I did that (8.1.6) and after that, still the same issue with phpcs as I mentioned above.

@shochdoerfer Thanks for the suggestion - that worked. Recreating the DDEV CLI interpreter instead of relying on the one that this project provides did the trick. Obviously, this makes me think that maybe there's something that has been updated in PhpStorm that breaks that particular bit of functionality in the plugin? I'm using PhpStorm 2023.1.3

-mike

[rfay]

Congrats on the progress! I think creating new configs in PhpStorm is often the ticket.

[nico-loeber]

Hey @shochdoerfer,

My guess would be, that the php info cache got lost and was not automatically regenerated.
The PHPInfo Cache is created by the plugin on any change to the interpreter configuration and is often triggert when clicking ddev restart in the UI. You can see a progress bar for a short period of time saying something like "Checking PHP Installation" or something like that.
I was not able to reproduce this error. Maybe a PHPStorm update cleared this cache? Is the problem solved after updating the cache (The progress bar popup appeared)?

Sorry for my late reply.

[shochdoerfer]

@nico-loeber no worries, since we found a way to fix it manually, we are fine. Would have pinged via other channels if we urgently needed a fix ;)

The weird thing is that we can reproduce the issue just in one of our projects but across all developer machines (no shared .idea directories via Git). Will check if cache cleaning fixes the problem. Thanks for your insights! Really awesome plugin btw.

[Kayu84]

came here cause i found an solution for me, doing the same "manual" fix described here:
https://blog.bitexpert.de/blog/ddev_intellij_plugin_phpunit_error

Since I was running out of ideas, I decided to create a new CLI Interpreters entry myself and copy all the data from the entry created by DDEV. Once I was done, I configured PHPUnit to use the newly created CLI Interpreter. And guess what? This time it worked. I informed my colleague, and the "fix" also worked on this machine. Problem solved.

watching this issue and hope for a fix in future.

Just an additional information:
came to this issue cause i tried to use php-cs-fixer with DDEV-Integration CLI-Interpreter:
In addition to the manual desribed fix i needed to add an manual PHP CS Fixer Setting beside the "System PHP", with PHP CS Fixer path: "./vendor/bin/php-cs-fixer". After that, the "Validate"-Button works too and i can use php-cs-fixer.

[rfay]

This class of fix has been reported in the PhpStorm issue queue as well. https://youtrack.jetbrains.com/issue/WI-73058

Great to know about the workaround here. So PHP CS Fixer is the answer? Can you give a more complete writeup of your solution? Maybe also reply in that PhpStorm issue.

[Kayu84]

@rfay: I know about the youtrack, just wanted to share my workaround (Stephan's) workaround.
No, php-cs-fixer is not the solution. But I wanted to use php-cs-fixer with DDEV Integration. (In Case of cli Interpreter, PHP Version from docker-compose: https://www.jetbrains.com/help/phpstorm/using-php-cs-fixer.html#installing-configuring-php-cs-fixer)

[rfay]

Right, if you could give a complete answer for a novice user, explaining all the things, it would be awesome. Remember not all of us are as engaged with either PhpStorm or PHP or testing as you are, thanks!