PHP unit and integration tests for Wikia app are automatically executed for each pull request by the Travis CI continuous integration system. If you'd like to run them locally, the following steps should help you get started:

1. Make sure you have PHP 7.0 installed. On macOS, this is easiest to do via Homebrew:

   $ brew install php@7.0
   $ echo 'export PATH="/usr/local/opt/php@7.0/bin:$PATH"' >> ~/.bash_profile
   $ echo 'export PATH="/usr/local/opt/php@7.0/sbin:$PATH"' >> ~/.bash_profile
   $ source ~/.bash_profile
   

2. Install at least the uopz and xdebug extensions from PECL and make sure your php instance have mysql extension insalled:

   $ pecl install uopz xdebug
   $ apt-get install php-mysql
   

3. Make sure you have a local MySQL server running.
4. Make sure that the parent directory of your app clone does NOT contain a config subdirectory with anything of value. The tests will write to this directory and destroy everything there!

You may need to set up MySQL account permissions:

GRANT ALL ON firefly.* TO 'your_username'@'localhost';
GRANT SUPER ON *.* TO 'your_username'@'localhost';

Once you got your environment setup, run the tests with:

$ ./php-tests.sh

If you have set custom credentials for your MySQL server, use the MYSQL_USER and MYSQL_PASSWORD environment variables to pass them to the test runner.

In order to run only a subset of all tests, pass a directory or file to the test runner as an argument:

$ ./php-tests.sh ../extensions/wikia/Example # run tests for Example only
$ ./php-tests.sh ../extensions/wikia/Example/tests/MyTest.php # run only MyTest

If you add a test which relies on PHP extensions to function (e.g. a test that involves rendering mustache templates), check if the extension is loaded in the test setup phase.

use PHPUnit\Framework\TestCase;

class MyTest extends TestCase {
	protected function setUp() {
		parent::setUp();

		if ( !extension_loaded( 'mustache' ) ) {
			$this->markTestSkipped( '"mustache" PHP extension needs to be loaded!' );
		}
	}
}

This way, the test will be gracefully skipped if the required extension is not available locally.

First fetch the dependencies from NPM:

$ npm install

Then you can run the tests with:

$ ./js-all