PHPSTORM DOCKERFILE CODE
Depending on the exact PHP image and exact platform, the root access within the container is necessary for the correct work of the code coverage plugin. Php_cli container should be inherited from the PHP container or be its copy. You may use any other image for PHP as a basis. jekakm/php71-core:201807161 image is our studio image for PHP container. # It is a temporary solution until it be fixed in new releases of PhpStorm. # Because PhpStorm recreates the php container every time it runs a script. Volumes : - "./docker-configs/php-fpm.ini:/etc/php/7.1/fpm/php.ini" - "./docker-configs/php-cli.ini:/etc/php/7.1/cli/php.ini" - ".:/app:cached" # This container should be used for running php scripts inside PhpStorm. The configuration, in this case, looks like this:Įnvironment : - "PHP_IDE_CONFIG=serverName=project-name-docker" At the same time, your major PHP container will not be killed, and you will be able to run your code from the web browser (or any other client for HTTP calls). You need to create another PHP container which will be used solely for Run/Debug Configurations in PhpStorm. To evade this side effect till JetBrains developers solve it, the community has worked out the easiest solution. When you write tests and features in IDE and then run tests, and after that switch to the browser and test the feature manually, you need to restart PHP container by hand because PhpStorm stops it after running your console script from the Run/Debug menu. This approach makes permanent development impossible. Project_name_php_cli_1 exited with code 0Īborting on container exit. Generating code coverage report in Clover XML format. 1 by Sebastian Bergmann and contributors. It can be observed from the results of test running from PhpStorm:ĭocker -compose : //:php_cli/php verage_enable=1 /app/vendor/phpunit/phpunit/phpunit -coverage-clover /opt/phpstorm-coverage/ProjectName$Run_all_tests.xml -configuration /app/ -teamcity Briefly, the matter is that when you set up running of Run Configuration from Docker, PhpStorm restarts the container with PHP any time the script is performed in it, and after that, the container is stopped. I recommend you to subscribe to them to remain informed. There is an issue where users suggest possible solutions, and there is also an issue where the fix for this problem is being planned. It is a well-known drawback which is discussed here. The plugin also can highlight in green or red the lines in your files which, correspondingly, are covered or not covered by tests:įor this plugin to work correctly in PhpStorm with PHP CLI configured from the Docker container, a range of additional actions should be taken.įirst, so far, the work with the already running containers has not been implemented correctly yet. That’s what the plugin in the form of a table with file and directory navigation shows. Using these statistics, we can calculate the percentage of the test code coverage since if there are operators in the file which have never been called during the tests, then, this piece of code is not covered by tests. This report will contain the information about the number of calls to each operator during tests execution. PhpUnit can be run with the options for generating code coverage report. There is a plugin PHPUnit Code Coverage which is used to display the code coverage with the PhpStorm tests. Let’s discuss how to fine-tune this process by means of Docker. One of such operations is running unit tests in the course of development. It allows the project participants to share common configurations using a ‘Shared’ flag in the settings. In PhpStorm, there is a possibility to create Run/Debug Configurations and to run them from IDE.
0 kommentar(er)
