Testing with Codeception
PhpStorm provides support for running unit, functional, and acceptance tests with the Codeception test framework, versions 2.2.0 and later.
Before you start
Downloading and installing Codeception
Before you start, make sure Composer is installed on your machine and initialized in the current project as described in Composer Dependency Manager.
Download and install Codeception manually
Download codeception.phar at the Codeception Installation page and save it under the root of the project where Codeception will be later used.
You can also save codeception.phar in a different location and configure it as an include path. In either case, PhpStorm will include codeception.phar in indexing, so it will successfully resolve references to the Codeception classes and thus provide you with full coding assistance.
Download and install Codeception with Composer
From the context menu of composer.json, choose . Alternatively choose from the main menu.
In the Manage Composer Dependencies Dialog that opens, select the
codeception/codeceptionpackage from the Available Packages list, possibly using the search field.
Choose the relevant version from the Version to install list.
If necessary, expand the Settings hidden area and specify the advanced installation options. In the Command line parameters field, type the additional command line parameters. It is recommended to provide the
--dev, option: the package in this case is added to the
require-devsection of the composer.json file instead of the default
Learn more about installing Codeception from Codeception Official website.
Initializing Codeception in a PhpStorm project
Having installed Codeception, you need to initialize it in your project by generating a codeception.yml configuration file.
Generate a codeception.yml configuration file
Open the built-in PhpStorm Terminal (Alt+F12) and at the command prompt type one of the following commands depending on the installation mode and your current operating system:
If you installed codeception.phar in your project, type
php codecept.phar bootstrapfor Windows and macOS or
codecept bootstrapfor Linux.
If you installed Codeception globally through Composer, type
codecept bootstrapfor all platforms.
Integrating Codeception with PhpStorm in a project
If you use a local PHP interpreter, PhpStorm performs initial Codeception configuration automatically.
Configure Codeception automatically
Store the codeception.yml or codeception.yml.dist configuration file under the project root.
You can configure Codeception manually. If you use a remote PHP interpreter, manual configuration is required.
Configure Codeception manually
In the Settings/Preferences dialog (Ctrl+Alt+S), expand the node and select under .
On the Test Frameworks page that opens, click in the central pane and choose the configuration type from the list:
In local configurations, the default project PHP interpreter is used, see Default project CLI interpreters for details.
To use Codeception with a remote PHP interpreter, choose one of the configurations in the dialog that opens:
In the Codeception Library area, specify the location of the Codeception executable file or codeception.phar archive in the target environment. For example, if you installed Codeception through Composer, the executable file is stored in vendor/bin/codecept. Click next to the Path to Codeception directory or phar file field. PhpStorm detects the version of Codeception and displays it below the field.
In the Test Runner area, appoint the configuration YML file to use for launching and executing scenarios.
By default, Codeception looks for a codeception.yml configuration file in the project root folder. You can appoint a custom configuration file.
Clear the Default configuration file checkbox to have Codeception use the codeception.yml configuration file from the project root folder. If no such file is found, test execution fails, therefore it may be more reliable to specify the configuration file explicitly.
Select the Default configuration file checkbox to specify your own YML configuration file. This file will be later used as default in all Codeception run/debug configurations.
In the field, specify the location of the configuration file to use. Type the path manually or click and choose the file in the dialog that opens.
Generating a Codeception test for a class
Open the Create New PHP Test dialog by doing any of the following:
On the main menu, choose PHP Test | Codeception Unit Test or PHP Test | Codeception Functional Test from the context menu.. Then, choose either
In the Project tool window, press Alt+Insert or right-click the PHP class to be tested and choose either New | PHP Test | Codeception Unit Test or New| PHP Test | Codeception Functional Test.
In the editor of the PHP class to be tested, position the caret inside the definition of the class. Then, choose Go To | Test from the context menu or press Ctrl+Shift+T and select Create New Test from the popup menu. This way, you can generate a test for a PHP class defined among several classes within a single PHP file.
To create a test for a certain method, position the caret within the method declaration. The chosen method will be automatically selected in the Generate test methods for area of the Create New PHP Test dialog.
The Create New PHP Test dialog opens.
Provide the parameters of the generated test:
The test file template, that is, the template based on which PhpStorm will generate the test class. Make sure that either Codeception Unit or Codeception Functional is selected in the Test file template list.
The fully qualified name of the class to be tested, this name will be used to propose the Test Class Name. By default, the Name box displays the name of the class on which the test generation was invoked. To use completion, press Ctrl+Space.
The name of the test class. PhpStorm automatically composes the name from the production class name as <production class>Test.php (for Codeception Unit Test) or <production class>Cest.php (for Codeception Functional Test). The test class name is displayed in the Name field of the Test Class area.
The folder for the test class. By default, it is the folder that is marked as a test sources root. If no such folder is specified, the folder containing the production class is proposed instead.
To specify a different folder, click next to the Directory field and choose the relevant folder.
The production class methods to generate test method stubs for. In the Generate test methods for area, select the checkboxes next to the required production class methods. To include inherited methods from parent classes, select the Show inherited methods checkbox.
PhpStorm will automatically compose the test methods' names as
test<production method>. You can customize the code templates used for generating test method stubs on the Code tab of the File and Code Templates settings page.
Check, accept, or update the predefined settings and click OK to initiate the test generation.
When the test is ready, you can navigate back to the production class by choosing Navigate | Go to Test Subject. For details, see Navigating Between Test and Test Subject.
Running and debugging Codeception tests
Run or debug Codeception tests
In the Project tool window, select the file or folder to run your tests from and choose Run '<file or folder>' or Debug '<file or folder>' from the context menu of the selection:
PhpStorm generates a default run configuration and starts a run/debug test session with it.
Save an automatically generated default configuration
After a test session is over, choose Save <default_test_configuration_name> from the context menu of the file or folder.
Run or debug tests through a previously saved run/debug configuration
Choose the required Codeception configuration from the list on the toolbar and click or .
Create a custom run/debug configuration
In the Project tool window, select the file or folder with the tests to run and choose Create run configuration from the context menu. Alternatively, choose on the main menu, then click and choose Codeception from the list.
In the Run/Debug Configuration: Codeception dialog that opens, specify the scenarios to run and customize the behavior of the current PHP interpreter by specifying the options and arguments to be passed to the PHP executable file.
Monitoring test results
The tab is divided into 2 main areas:
The left-hand area lets you drill down through all unit tests to see the succeeded and failed ones. You can filter tests, export results, and use the context menu commands to run specific tests or navigate to the source code.
The right-hand area displays the raw Codeception output.