PhpStorm and QFQ » History » Revision 8
Revision 7 (Marc Egger, 18.12.2018 17:41) → Revision 8/9 (Carsten Rose, 10.01.2024 14:55)
h1. PhpStorm and QFQ
{{child_pages}}
{{toc}}
h2. Configure Remote Deployment
!settings-deployment-webwork.png!
!settings-deployment-webwork-mappings.png!
h3. Automatically upload changes to server (Convenient):
!settings-auto-deploy.png!
h2. Configure Remote Interpreter
!settings-php.png!
!settings-CLI-Interpreter-Remote-PHP.png!
h2. Configure Remote Debug
!settings-servers-path-mapping.png!
h2. Configure and Run Remote Phpunit Test
First manually copy phpunit.phar to some location on the server which you may access (NOT into extension directory! Safety hazard!)
Then configure remote unittesting on in PhpStorm:
!settings-phpunit-remote.png!
h3. Run Tests
To run all the tests: run phpunit.xml which is located in the extension folder (right click -> run)
Run tests with code coverage: run phpunit.xml with Coverage (right click -> green arrow with shield)
Run only one test class: directly run that class (right click -> run)
h1. Issues
h2. Debugging: PhpStorms always shows sources for `typo3_src/index.php` from an outdated T3 version.
* Happens to PG (thinlinc environment) on Docker U22 installation on webwork20 after migration from a U20 docker to U22.
* We've checked 'Settings > Directories' and 'Debug > ... > path mappings' - all occurences ofT3 V10 (old and unwanted) has been removed.
* Creating new 'debug profile' and new 'server/path mapping profile' helped.
* Restarting PhpStorm did not helped
* Renamed the T3 V10 source folder so that PhpStorm could not access it anymore - than the PS asked for a new path and than we're able to define the new version.
* Problem solved.