Clear reports gives a picture of the current state of the system. Which tests are passed, which tests are failed, and if failed what was the reason. Reports may vary on the level of detail and by the technical information collected. Codeception provides as built-in reporters and customizable API to create your own reporter.


The standard reporter you already is CLI reporter. It is great for writing and debugging tests as well, as checking the results on CI. On failure, CLI reporter prints a list of all failed tests, if test includes some valuable data like last send requests for REST module, it will also be printed under ‘artifacts’ section of a test.

To launch CLI reporter in minimal mode, simply execute tests:

php vendor/bin/codecept run 

To see step-by-step execution in a runtime use --steps flag:

php vendor/bin/codecept run --steps

To get additional information which may be handful for debugging tests use --debug flag. This flag is your best friend for writing new tests.

php vendor/bin/codecept run --debug

More CLI options are available:

  • Artifacts report can be disabled with --no-artifacts option.
  • To explicitly enable ANSI colors use --colors, and --no-colors to disable them.
  • Use --silent to get the minimal possible output

Codeception will exit with exit code 1 if tests are failed. This is how CI can mark the job as failed.


More information can be presented via HTML report.

Run tests with --html flag to create html report

php vendor/bin/codecept run --html

HTML report is valuable to present for non-tech colleagues. If you create HTML reports on CI you need to store a report as artifact to display it after. Codeception generates a static HTML file so no additional web server is needed to show it.

While HTML report can be pretty good for a single test run, more advanced reporting can be enabled by using is a SaaS service which can store and present reports, and could be used by developers, QAs and managers. It is a complete test management system, which allows you track the history of tests, detect flaky tests, and work on planning new tests. reports are easy to set up and without storing artifacts on CI system.

😻 is free for small teams, so you can use its reporting features with Codeception. imports all tests into UI, so your managers, business analysts, and manual QAs can see all your unit, funcitonal, and acceptance tests listed in one place:

To start, create a new project at and import all your Codeception tests into it. Install testomatio packages for reporting and importing Codeception tests:

composer require testomatio/list-tests --dev
composer require testomatio/reporter --dev

Obtain API key from a newly created project and import tests:

TESTOMATIO={apiKey} php vendor/bin/list-tests tests

After tests imported you can get a complete report while executing them:

TESTOMATIO={apiKey} php vendor/bin/codecept run --ext "Testomatio\Reporter\Codeception"

Data from test runs will be sent to server and you will see tests statuses are reported in realtime. not only provides reports for test executions, it also collects historical data for tests, allows attaching tests to Jira issues, and provides useful analytics, and allows planning new tests.

Check an Example Project to try it.


By default Codeception saves the screenshot for a failed test for acceptance tests and show it in HTML report. However, can’t be possible to understand cause of failure just by one screenshot. This is where Recorder extension is handy, it saves a screenshot after each step and shows them in a slideshow.

Selenium WebDriver doesn’t have a simple way to record a video of a test execution, so slideshow is the simplest solution you can use to debug your tests.

To use Recorder enable it as an extension inside config file:

        - Codeception\Extension\Recorder

More config options are available on Extension page.


JUnit XML is a reporting standard for testing frameworks. CI platforms like Jenkins can visualize JUnit reports.

php vendor/bin/codecept run --xml


Allure is a popular open-source reporting tool. It can be paired with Codeception to get a detailed run report. Use Allure extension to generate report which can be passed to Allure to display it.

Custom Reporter

Custom reporter can be built as an Extension. Extension can listen to all test events and log data from them. Look into the basic reporting extensions like DotReporter or Logger to learn how to build your own.

Use them to change output or use them as an example to build your own reporter. They can be easily enabled with --ext option

php vendor/bin/codecept run --ext DotReporter

If you want to use it as default reporter enable extension in codeception.yml.

Don't know how to write tests on your own? We will build or improve them for you. Request a quote for official enterprise support or trainings