test

request() method (refer to More request methods) returns a Crawler object, Used to select elements from response content and complete actions such as clicking a link or submitting a form.

When you need to click a link, first use the grabber to select it. You can use XPath expressions or CSS pickers to complete the selection, and then use client behavior to click it:

$link = $crawler
    ->filter('a:contains("Greet")') // 选择所有含有"Greet"文本之链接
    ->eq(1) // 结果列表中的第二个
    ->link() // 点击它; $crawler = $client->click($link);

Submitting a form is very similar: select a form button, optionally override the values ​​of some form items, and then submit the corresponding form:

$form = $crawler->selectButton('submit')->form(); // 设置一些值$form['name'] = 'Lucas';$form['form_name[subject]'] = 'Hey there!'; // 提交表单$crawler = $client->submit($form);

Now you can easily move through your program, using assertions to test whether the page behaves as you expect. Use a Crawler to make assertions act on the DOM.

// Assert that the response matches a given CSS selector.// 断言响应内容匹配到一个指定的CSS拾取器$this->assertGreaterThan(0, $crawler->filter('h1')->count());

Or test the response content directly, if you just want to assert whether the content contains certain text, or just know that the response content is not in XML/HTML format:

$this->assertContains(
    'Hello World',
    $client->getResponse()->getContent());

use Symfony\Component\HttpFoundation\Response; // ... // Assert that there is at least one h2 tag// with the class "subtitle"// 断言至少有一个h2标签，其class是subtitle$this->assertGreaterThan(
    0,
    $crawler->filter('h2.subtitle')->count()); // Assert that there are exactly 4 h2 tags on the page// 断言页面有4个h2标签$this->assertCount(4, $crawler->filter('h2')); // Assert that the "Content-Type" header is "application/json"// 断言Content-Type头是application/json$this->assertTrue(
    $client->getResponse()->headers->contains(
        'Content-Type',
        'application/json'
    )); // Assert that the response content contains a string// 断言响应信息中包含一个字符串$this->assertContains('foo', $client->getResponse()->getContent());// ...or matches a regex$this->assertRegExp('/foo(bar)?/', $client->getResponse()->getContent()); // Assert that the response status code is 2xx// 断言响应状态码是2xx$this->assertTrue($client->getResponse()->isSuccessful());// Assert that the response status code is 404// 断言响应状态码是404$this->assertTrue($client->getResponse()->isNotFound());// Assert a specific 200 status code// 断言响应状态码是特殊的200$this->assertEquals(
    200, // or Symfony\Component\HttpFoundation\Response::HTTP_OK
    $client->getResponse()->getStatusCode()); // Assert that the response is a redirect to /demo/contact// 断言响应是一个指向/demo/contact的跳转$this->assertTrue(
    $client->getResponse()->isRedirect('/demo/contact'));// ...or simply check that the response is a redirect to any URL// 或者仅言响应是一个跳转，不管指向的URL是什么$this->assertTrue($client->getResponse()->isRedirect());

Use Test Client ¶

Test The client (test client) simulates an HTTP client, just like a browser, and can generate requests for your Symfony program.

1

$crawler = $client->request('GET', '/post/hello-world');

request() The method accepts an HTTP request parameter and a URL parameter, and returns a Crawler instance.

request(
    $method,
    $uri,
    array $parameters = array(),
    array $files = array(),
    array $server = array(),
    $content = null,
    $changeHistory = true)

$client->request(
    'GET',
    '/post/hello-world',
    array(),
    array(),
    array(
        'CONTENT_TYPE'          => 'application/json',
        'HTTP_REFERER'          => '/foo/bar',
        'HTTP_X-Requested-With' => 'XMLHttpRequest',
    ));

Use a scraper to find DOM elements in the response content. These elements can be used in occasions such as clicking links or submitting forms:

$link = $crawler->selectLink('Go elsewhere...')->link();$crawler = $client->click($link); $form = $crawler->selectButton('validate')->form();$crawler = $client->submit($form, array('name' => 'Fabien'));

The click() method and the submit() method here will both Returns a crawler crawler object. These methods are the best way to browse your application's pages because they do a lot of things for you, like detect HTTP request patterns from forms, or provide you with a nice API for file uploads.

request method can also be used to directly simulate form submission, or to perform more complex requests. Some useful examples:

// Directly submit a form (but using the Crawler is easier!)// 直接提交表单（但是使用Crawler更容易些）$client->request('POST', '/submit', array('name' => 'Fabien')); // Submit a raw JSON string in the request body// 在请求过程中提交一个JSON原生串$client->request(
    'POST',
    '/submit',
    array(),
    array(),
    array('CONTENT_TYPE' => 'application/json'),
    '{"name":"Fabien"}'); // Form submission with a file upload// 文件上传表单的提交use Symfony\Component\HttpFoundation\File\UploadedFile; $photo = new UploadedFile(
    '/path/to/photo.jpg',
    'photo.jpg',
    'image/jpeg',
    123);$client->request(
    'POST',
    '/submit',
    array('name' => 'Fabien'),
    array('photo' => $photo)); // Perform a DELETE request and pass HTTP headers// 执行一个DELETE请求并传递HTTP头$client->request(
    'DELETE',
    '/post/12',
    array(),
    array(),
    array('PHP_AUTH_USER' => 'username', 'PHP_AUTH_PW' => 'pa$$word'));

As a final reminder, you can force each request to be executed in their own PHP process to avoid side effects when there are multiple clients in the same script.

1

$crawler = $client->request('GET', '/post/hello-world');

Browsing ¶

Client object supports many operations in real browsers:

$client->back();$client->forward();$client->reload(); // Clears all cookies and the history// 清除所有cookie和历史记录$client->restart();

Use internal Object ¶

getInternalRequest() and getInternalResponse() methods were introduced from Symfony 2.3. If you use the client to test your program, you may want to use some objects inside the client:

$history = $client->getHistory();$cookieJar = $client->getCookieJar();

You can also get the object related to the most recent request:

// the HttpKernel request instance// HttpKernel的请求实例$request = $client->getRequest(); // the BrowserKit request instance// 浏览器组件的请求实例$request = $client->getInternalRequest(); // the HttpKernel response instance// HttpKernel的响应实例$response = $client->getResponse(); // the BrowserKit response instance// 浏览器组件的响应实例$response = $client->getInternalResponse(); $crawler = $client->getCrawler();

If your request is not running in isolation, you can also use Container (container) and Kernel (kernel):

$container = $client->getContainer();$kernel = $client->getKernel();

Using containers ¶

It is strongly recommended that functional testing only tests the response. But in certain rare cases, you may want to use internal objects to write assertions. At this time, you can call Dependency Injection Container (dependency injection container, that is, service container):

1

$client->insulate();

1

$container = $client->getContainer();

$form = $buttonCrawlerNode->form(array(
    'name'              => 'Fabien',
    'my_form[subject]'  => 'Symfony rocks!',));

Client is responsible for submitting the form instance:

The value of the field can be passed to the second parameter of the submit() method:

$client->submit($form, array(
    'name'              => 'Fabien',
    'my_form[subject]'  => 'Symfony rocks!',));

For more complex situations, the form instance can be used as an array to set it separately. The value corresponding to each field:

// 改变某个字段的值/Change the value of a field$form['name'] = 'Fabien';$form['my_form[subject]'] = 'Symfony rocks!';

There is also a very useful API that can manage their values ​​​​according to the field type:

// 选取一个option单选或radio单选$form['country']->select('France'); // 选取一个checkbox$form['like_symfony']->tick(); // 上传一个文件$form['photo']->upload('/path/to/lucas.jpg');

Add or delete forms to Collection ¶

If you use Collection of Forms (form collection) , you Cannot add a $form['task[tags][0][name]'] = 'foo field to an existing form. This results in an Unreachable field "…" error. Because $form can only be used to set existing fields. In order to add a new field, you have to add the value to a primitive array:

// Get the form. 取得表单$form = $crawler->filter('button')->form(); // Get the raw values. 取得原始数值$values = $form->getPhpValues(); // Add fields to the raw values. 给原始数组添加新字段$values['task']['tag'][0]['name'] = 'foo';$values['task']['tag'][1]['name'] = 'bar'; // Submit the form with the existing and new values.// 提交表单，包括既有值，以及新值$crawler = $this->client->request($form->getMethod(), $form->getUri(), $values,
    $form->getPhpFiles()); // The 2 tags have been added to the collection.// 2个新标签被添加到collection中$this->assertEquals(2, $crawler->filter('ul.tags > li')->count());

Here task[tags][0][name] is the field created by JavaScript name.

You can remove an existing field, such as a tag:

// Get the values of the form. 取得表单数据$values = $form->getPhpValues(); // Remove the first tag. 移除第一个标签unset($values['task']['tags'][0]); // Submit the data. 提交数据$crawler = $client->request($form->getMethod(), $form->getUri(),
    $values, $form->getPhpFiles()); // The tag has been removed. 标签已被移除$this->assertEquals(0, $crawler->filter('ul.tags > li')->count());

Configuration test ¶

The Client used in functional testing creates a Kernel for running in a special test test environment. Since Symfony loads app/config/config_test.yml when testing, you can adjust any "program-level" settings used for testing.

For example, the default Swift Mailer is set not to send emails in a test environment. The relevant options in the configuration file are set like this:

PHP:// app/config/config_test.php // ...$container->loadFromExtension('swiftmailer', array(
    'disable_delivery' => true,));

XML:<!-- app/config/config_test.xml --><?xml version="1.0" encoding="UTF-8" ?><container xmlns="http://symfony.com/schema/dic/services"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"    xmlns:swiftmailer="http://symfony.com/schema/dic/swiftmailer"    xsi:schemaLocation="http://symfony.com/schema/dic/services        http://symfony.com/schema/dic/services/services-1.0.xsd        http://symfony.com/schema/dic/swiftmailer        http://symfony.com/schema/dic/swiftmailer/swiftmailer-1.0.xsd">     <!-- ... -->
    <swiftmailer:config disable-delivery="true" /></container>

YAML:# app/config/config_test.yml # ...swiftmailer:
    disable_delivery: true

You can also use a completely different environment, or override the default debug mode ( true ) by passing the relevant options to the createClient() method:

$client = static::createClient(array(
    'environment' => 'my_test_env',
    'debug'       => false,));

If your program requires some HTTP headers to run, pass them to the second parameter of the createClient() method:

$client = static::createClient(array(), array(
    'HTTP_HOST'       => 'en.example.com',
    'HTTP_USER_AGENT' => 'MySuperBrowser/1.0',));

You can also pass them in each request The basic process is to overwrite the HTTP header:

$client->request('GET', '/', array(), array(), array(
    'HTTP_HOST'       => 'en.example.com',
    'HTTP_USER_AGENT' => 'MySuperBrowser/1.0',));

PHPUnit configuration ¶

Each program has its own PHPUnit configuration, which exists in app/phpunit. xml.dist file. You can edit this file to change the default values, or create a app/phpunit.xml file that sets test options only for your local machine.

The default is only stored in the standard directory (src//Bundle/Tests, src//Bundle/Bundle/Tests, src/ *Bundle/Tests) The tests in your custom bundle can be executed by the phpunit command. This is already configured in the app/phpunit.xml.dist file:

<!-- app/phpunit.xml.dist --><phpunit>
    <!-- ... -->
    <testsuites>
        <testsuite name="Project Test Suite">
            <directory>../src/*/*Bundle/Tests</directory>
            <directory>../src/*/Bundle/*Bundle/Tests</directory>
            <directory>../src/*Bundle/Tests</directory>
        </testsuite>
    </testsuites>
    <!-- ... --></phpunit>

But you can easily add more directories. For example, the following configuration adds tests in the custom directory lib/tests:

<!-- app/phpunit.xml.dist --><phpunit>
    <!-- ... -->
    <testsuites>
        <testsuite name="Project Test Suite">
            <!-- ... - - ->            <directory>../lib/tests</directory>        </testsuite>    </testsuites>    <!-- ... - - -></phpunit>

In order to include other directories in code coverage, you also need to add a code segment:

<!-- app/phpunit.xml.dist --><phpunit>
    <!-- ... -->
    <filter>
        <whitelist>
            <!-- ... -->
            <directory>../lib</directory>
            <exclude>
                <!-- ... -->
                <directory>../lib/tests</directory>
            </exclude>
        </whitelist>
    </filter>
    <!-- ... - - -></phpunit>

php.cn

HomeCourseArticleQ&ADictionaryManualDownloadsearch APPDownload

1

$client->submit($form);