# Plugin testing Plugin unit tests can be performed by running `phpunit` in the base plugin directory. ### Creating plugin tests Plugins can be tested by creating a creating a file called `phpunit.xml` in the base directory with the following content, for example, in a file **/plugins/acme/blog/phpunit.xml**: ./tests Then a **tests/** directory can be created to contain the test classes. The file structure should mimic the base directory with classes having a `Test` suffix. Using a namespace for the class is also recommended. 'Hi!']); $this->assertEquals(1, $post->id); } } The test class should extend the base class `PluginTestCase` and this is a special class that will set up the October database stored in memory, as part of the `setUp()` method. It will also refresh the plugin being testing, along with any of the defined dependencies in the plugin registration file. This is the equivalent of running the following before each test: php artisan october:up php artisan plugin:refresh Acme.Blog [php artisan plugin:refresh , ...] # System testing ### Unit tests Unit tests can be performed by running `phpunit` in the root directory or inside `/tests/unit`. ### Functional tests Functional tests can be performed by running `phpunit` in the `/tests/functional` directory. Ensure the following configuration is met: - Active theme is `demo` - Language preference is `en` #### Selenium set up 1. Download latest Java SE from http://java.sun.com/ and install 1. Download a distribution archive of [Selenium Server](http://seleniumhq.org/download/). 1. Unzip the distribution archive and copy selenium-server-standalone-2.42.2.jar (check the version suffix) to /usr/local/bin, for instance. 1. Start the Selenium Server server by running `java -jar /usr/local/bin/selenium-server-standalone-2.42.2.jar`. #### Selenium configuration Create a new file `selenium.php` in the root directory, add the following content: