When running tests “with Coverage” in any #JetBrains IDE, where does it store the coverage files?
My project is running in containers with docker compose, and this is all set up properly. In fact, the tests run, and presumably, the coverage report is generated, but the IDE doesn’t show the coverage, and I think it’s because it must be storing the coverage report on the container somewhere, and the IDE can’t access it when trying to display the lines covered.
@tjventurini Depends… PHPStorm for laravel and other framework projects. VS Code for small single file scripts, or small frameworkless projects and testing quick one offs. No reason you can’t use both right?
Is it just me or is #phpstorm getting worse by the day?
I'm runnig 2024.1 (Build #PS-241.14494.237, built on March 27, 2024) but have to constantly restart the IDE to fix bizarre errors like PHPStorm claiming a property or parameter isn't used while highlighting the very use a line later, inconsistently resolving asserts with instanceof checks - e.g. claiming a method doesn't exist in the class referenced in a different assert and not seeing a parameter that is clearly there... #fail#ensh11n
I've been getting this popup in my #PhpStorm for the last couple of days.
Obviosuly I know why this is happening (NextDNS blocking the request) but I can't see any other info, such as which component is making that call, which URL is actually being requested etc.
Nor is there a way to stop this (clicking 'Reject' just makes the thing pop back up a few seconds later).