Introduction

This Bundle provides base classes for functional tests to assist in setting up test-databases, loading fixtures and HTML5 validation. It also provides a DI aware mock builder for unit tests.

Installation

1. Download the Bundle

   Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:

   $ composer require --dev liip/functional-test-bundle

   This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.

2. Enable the Bundle

   Add the following line in the app/AppKernel.php file to enable this bundle only for the test environment:

   <?php
   // app/AppKernel.php
   
   // ...
   class AppKernel extends Kernel
   {
       public function registerBundles()
       {
           // ...
           if (in_array($this->getEnvironment(), array('dev', 'test'))) {
               $bundles[] = new Liip\FunctionalTestBundle\LiipFunctionalTestBundle();
           }
   
           return $bundles
       }
   
       // ...
   }

3. Enable the functionalTest service adding the following empty configuration:

   # app/config/config_test.yml
   liip_functional_test: ~

   Ensure that the framework is using the filesystem for session storage:

   # app/config/config_test.yml
   framework:
       test: ~
       session:
           storage_id: session.storage.filesystem

Database Tests

If you plan on loading fixtures with your tests, make sure you have the DoctrineFixturesBundle installed and configured first: Doctrine Fixtures setup and configuration instructions

In case tests require database access make sure that the database is created and proxies are generated. For tests that rely on specific database contents, write fixture classes and call loadFixtures() method from the bundled Test\WebTestCase class. This will replace the database configured in config_test.yml with the specified fixtures. Please note that loadFixtures() will delete the contents from the database before loading the fixtures. That's why you should use a designated database for tests.

Tips for Fixture Loading Tests

SQLite

1. If you want your tests to run against a completely isolated database (which is recommended for most functional-tests), you can configure your test-environment to use a SQLite-database. This will make your tests run faster and will create a fresh, predictable database for every test you run.

   # app/config/config_test.yml
   doctrine:
       dbal:
           default_connection: default
           connections:
               default:
                   driver:   pdo_sqlite
                   path:     %kernel.cache_dir%/test.db

2. In order to run your tests even faster, use LiipFunctionalBundle cached database. This will create backups of the initial databases (with all fixtures loaded) and re-load them when required.

   Attention: you need Doctrine >= 2.2 to use this feature.

   # app/config/config_test.yml
   liip_functional_test:
       cache_sqlite_db: true

3. Load your Doctrine fixtures in your tests:

   use Liip\FunctionalTestBundle\Test\WebTestCase;
   
   class MyControllerTest extends WebTestCase
   {
       public function testIndex()
       {
           // add all your fixtures classes that implement
           // Doctrine\Common\DataFixtures\FixtureInterface
           $this->loadFixtures(array(
               'Bamarni\MainBundle\DataFixtures\ORM\LoadData',
               'Me\MyBundle\DataFixtures\ORM\LoadData'
           ));
   
           // you can now run your functional tests with a populated database
           $client = static::createClient();
           // ...
       }
   }

4. If you don't need any fixtures to be loaded and just want to start off with an empty database (initialized with your schema), you can simply pass an empty array to loadFixtures.

   use Liip\FunctionalTestBundle\Test\WebTestCase;
   
   class MyControllerTest extends WebTestCase
   {
       public function testIndex()
       {
           $this->loadFixtures(array());
   
           // you can now run your functional tests with a populated database
           $client = static::createClient();
           // ...
       }
   }

5. This bundle uses Doctrine ORM by default. If you are using another driver just specify the service id of the registry manager:

   use Liip\FunctionalTestBundle\Test\WebTestCase;
   
   class MyControllerTest extends WebTestCase
   {
       public function testIndex()
       {
           $fixtures = array(
               'Me\MyBundle\DataFixtures\MongoDB\LoadData'
           );
   
           $this->loadFixtures($fixtures, null, 'doctrine_mongodb');
   
           $client = static::createClient();
       }
   }

Non-SQLite

The Bundle will not automatically create your schema for you unless you use SQLite. If you prefer to use another database but want your schema/fixtures loaded automatically, you'll need to do that yourself. For example, you could write a setUp() function in your test, like so:

use Doctrine\ORM\Tools\SchemaTool;
use Liip\FunctionalTestBundle\Test\WebTestCase;

class AccountControllerTest extends WebTestCase
{
    public function setUp()
    {
        $em = $this->getContainer()->get('doctrine')->getManager();
        if (!isset($metadatas)) {
            $metadatas = $em->getMetadataFactory()->getAllMetadata();
        }
        $schemaTool = new SchemaTool($em);
        $schemaTool->dropDatabase();
        if (!empty($metadatas)) {
            $schemaTool->createSchema($metadatas);
        }
        $this->postFixtureSetup();

        $fixtures = array(
            'Acme\MyBundle\DataFixtures\ORM\LoadUserData',
        );
        $this->loadFixtures($fixtures);
    }
//...
}

Without something like this in place, you'll have to load the schema into your test database manually, for your tests to pass.

Created already logged client

The WebTestCase provides a conveniency method to create an already logged client using $client = static::makeClient(true);

and providing in your config_test.yml the following

liip_functional_test:
    authentication:
        username: "a valid username"
        password: "the password of that user"

Note: the makeClient support more parameters if you need to log with different user (for example to test with one user that is Admin, one that is normal user etc.)

As recommended by the Symfony guide, it is already recommended to use HTTP Basic Auth for you test by putting in config_test.yml :

#the best practice in symfony is to put a HTTP basic auth
#for the firewall in test env, so that not to have to
#make a request to the login form every single time
#http://symfony.com/doc/current/cookbook/testing/http_authentication.html
security:
    firewalls:
        NAME_OF_YOUR_FIREWALL:
            http_basic: ~

for more details, you can check the implementation of WebTestCase in that bundle

HTML5 Validator

The online validator: http://validator.nu/ The documentation: http://about.validator.nu/ Documentation about the web service: http://wiki.whatwg.org/wiki/Validator.nu_Web_Service_Interface

Dependencies

To run the validator you require the following dependencies:

• A java JDK 5 or later
• Python
• SVN
• Mercurial

Note: The script wants to see a Sun-compatible jar executable. Debian fastjar will not work.

Compilation and Execution

Before starting:

• Set the JAVA_HOME environment variable to the root of the installed JDK
• Add the location of javac to your PATH ($JAVA_HOME/bin).
• Alternatively you can use the --javac=/usr/bin/javac parameter of the build.py script.

Then:

$ mkdir checker; cd checker
$ git clone https://github.com/validator/validator.git
$ cd validator
$ python ./build/build.py all; python ./build/build.py all

Note: Yes, the last line is there twice intentionally. Running the script twice tends to fix a ClassCastException on the first run.

Note: If at some point for some reason the compilation fails and you are forced to re-run it, it may be necessary to manually remove the htmlparser directory from your disk (the compilation process will complain about that).

This will download the necessary components, compile the validator and run it. This will require about 10 minutes on the first run.

Once the validator is executed it can be reached at http://localhost:8888/ Further instructions on how to build the validator can be found at http://validator.github.io/validator/#build-instructions.

Execution

Once the validator has been compiled, it can be run with the following command:

cd checker
python build/build.py run

Using the Validator in Functional Tests

The Liip\FunctionalTestBundle\Test\Html5WebTestCase class allows to write functional tests that validate content against the HTML5 validator. In order to work the validator service must be running on the machine where the tests are executed.

This class provides the following testing methods:

• validateHtml5: This runs a validation on the provided content and returns the full messages of the validation service (including warnings and information). This method is not meant as a test method but rather as a helper to access the validator service. Internally the test method below will use this helper to access the validation service.

• assertIsValidHtml5: This will validate the provided content. If the validation succeeds, execution silently continues, otherwise the calling test will fail and display a list of validation errors.

• assertIsValidHtml5Snippet: This will validate an HTML5 snippets (i.e. not a full HTML5 document) by wrapping it into an HTML5 document. If the validation succeeds, execution silently continues, otherwise the calling test will fail and display a list of validation errors.

• assertIsValidHtml5AjaxResponse: This will validate an AJAX response in a specific format (probably not generic enough). If the validation succeeds, execution silently continues, otherwise the calling test will fail and display a list of validation errors.

• setHtml5Wrapper: Allow to change the default HTML5 code that is used as a wrapper around snippets to validate

Query Counter

To catch pages that use way too many database queries, you can enable the query counter for tests. This will check the profiler for each request made in the test using the client, and fail the test if the number of queries executed is larger than the number of queries allowed in the configuration. To enable the query counter, adjust the config_test.yml file, setting the liip_functional_test.query_count.max_query_count setting, like this:

liip_functional_test:
    query_count.max_query_count: 50

That will limit each request executed within a functional test to 50 queries.

Maximum Query Count per Test

The default value set in the config file should be reasonable to catch pages with high query counts which are obviously mistakes. There will be cases where you know and accept that the request will cause a large number of queries, or where you want to specifically require the page to execute less than x queries, regardless of the amount set in the configuration. For those cases you can set an annotation on the test method that will override the default maximum for any requests made in that test.

To do that, include the Liip\FunctionalTestBundle\Annotations\QueryCount namespace and add the @QueryCount(100) annotation, where 100 is the maximum amount of queries allowed for each request, like this:

use Liip\FunctionalTestBundle\Annotations\QueryCount;

class DemoTest extends WebTestCase
{
    /**
     * @QueryCount(100)
     */
    public function testDoDemoStuff()
    {
        $client = static::createClient();
        $crawler = $client->request('GET', '/demoPage');

        $this->assertTrue($crawler->filter('html:contains("Demo")')->count() > 0);
    }
}

Only in Test Environment

All the functionality of this bundle is primarily for use in the test environment. The query counter specifically requires services that are only loaded in the test environment, so the service will only be loaded there. If you want to use the query counter in a different environment, you'll need to make sure the bundle is loaded in that environment in your AppKernel.php file, and load the test services by adding test to the framework configuration in the config.yml (or the configuration file for your environment):

framework:
    [...]
    test: ~

If that's not what you want to do, and you're getting an exception about this, check that you're really only loading this bundle in your test environment (See step 3 of the installation)

Caveats

• QueryCount annotations currently only work for tests that have a method name of testFooBla() (with a test prefix). The @test annotation isn't supported at the moment.

• Enabling the Query Counter currently breaks PHPUnit's built-in annotations, e.g. @dataProvider, @depends etc. To fix this, you need to hide the appropriate PHPUnit annotation from Doctrine's annotation reader using the @IgnoreAnnotation annotation:

Liip\FunctionalTestBundle\Test\WebTestCase;

/** * @IgnoreAnnotation("dataProvider") * @IgnoreAnnotation("depends") */ class DemoTest extends WebTestCase { // ... }