ezpublish-legacy-tests

eZ Publish Legacy Tests

Execute PHPUnit tests for eZ Publish Legacy, optionally with one or more
activated extensions.

How it works

With Phing a clean eZ Publish installation is
generated and PHPUnit tests are perfomed.

Details

• The eZ Publish legacy
  repository and all testable extensions get cloned/pulled into the cache
  directory
• The eZ Publish core files and the extensions get copied into the build
  directory.
• The extensions are activated and the PHPUnit tests for the whole
  installation are started

Build status

When the build is marked as failed, this means that eZ Publish Legacy or one
of the tested extensions did not pass the tests. Click on the badges to see
what the problem was.

Unfortunately, builds can not be triggered automatically as soon as one
of ezsystems' repositories is updated. So the Travis CI build status only
gets updated when triggered through a push here.

You can always clone this repository and perform the tests on your machine.

Testable extensions

• ezformtoken (included in eZ Publish LS)
• ezjscore (included in eZ Publish LS)
• ezoe (included in eZ Publish LS)
• ezcomments
• ezfind
• ezprestapiprovider

Requirements

MySQL and a test database

Out of the box, the script expects a MySQL server instance at 127.0.0.1, a database named ezpublish_test,
and user root with no password. If you want to override those values, copy the file config/config.properties to
config/config_local.properties and change the variables.

Composer

See the Composer Website for further information.

PHPUnit

See the PHPUnit Website for further information.

Installation

Clone this repository and install the dependencies

Usage

eZ Publish Legacy standalone with builtin extensions

eZ Publish Legacy with one additional extension

eZ Publish Legacy with multiple additional extensions