Run/Debug Configuration: PHPUnit by HTTP
Use this dialog box to configure running unit tests of PHP applications on a remote server.
PHP unit testing requires the following prerequisites to be fulfilled:
- The PHPUnit tool should be installed and configured on your machine.
PEARfolder should be added to the list of the project content roots.
Click here for the description of the options that are common for all run/debug configurations.
The dialog box contains the following tabs and areas:
In this tab, specify the unit tests to launch and the command line switches to be passed to the test runner.
In this area, specify the location of tests or the configuration file where they are listed.
|Test Runner options|
|Custom working directory||
In this text box, specify the location of the files that are outside the folder with tests and are referenced in your tests through relative paths.
Type the path manually or click the Browse button and select the desired folder in the dialog that opens.
This setting does not block the test execution because the location of tests is always specified through a full path to the corresponding files and/or directories.
Test Groups Tab
In this tab, appoint the groups of tests to execute when the tests are run according to the current run configuration.
Grouping tests is helpful, for example, to distinguish between tests to run in a production environment from those to run in your development environment. You just need to create two groups and then include or exclude them depending on the current environment.
To attach a test to a group, tag it with the @group annotation in the format:
/** @group <group specification> */
|Include/Exclude groups||Select this check box to enable configuring execution of test groups.|
|Group Name||In this read-only list, select the test group to be involved or skipped in testing.|
|Include||Select this check box to have the tests from the selected test group executed.|
|Exclude||Select this check box to have the tests from the selected test group skipped.|
In this tab, configure deployment of tests to a remote server.
In this field, specify the configuration through which the debugging engine will interact with the server through HTTP. Actually, a configuration consist of a URL address of the target environment,
the debugger type, and possibly mappings between folders in your project and their correspondences on the server.
Choose a configuration from the drop-down list or click the Browse button and define a new configuration in the Servers dialog box that opens.
|Upload test directory before run||
|Remove test files after run||
|Show transfer logs||Select this check box to have test deployment logged.|
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, PhpStorm checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.