moved profiling info in tests in the recipe

Author: fabpot

cookbook/testing/profiling.rst

@@ -1,28 +1,62 @@
 .. index::
    single: Tests; Profiling
 
-How to use the Profiling Data in a Test
-=======================================
+How to use the Profiler in a Functional Test
+============================================
 
 It's highly recommended that a functional test only tests the Response. But if
 you write functional tests that monitor your production servers, you might
-want to write tests on the profiling data.
+want to write tests on the profiling data as it gives you a great way to check
+various things and enforce some metrics.
 
 The Symfony2 :doc:`Profiler </guides/internals/profiler>` gathers a lot of
 data for each request. Use these data to check the number of database calls,
 the time spent in the framework, ... But before writing assertions, always
 check that the profiler is indeed available (it is enabled by default in the
 ``test`` environment)::
 
-    if ($profiler = $client->getProfiler()) {
-        // check the number of requests
-        $this->assertTrue($profiler->get('db')->getQueryCount() < 10);
+    class HelloControllerTest extends WebTestCase
+    {
+        public function testIndex()
+        {
+            $client = $this->createClient();
+            $crawler = $client->request('GET', '/hello/Fabien');
 
-        // check the time spent in the framework
-        $this->assertTrue( $profiler->get('timer')->getTime() < 0.5);
+            // Write some assertions about the Response
+            // ...
+
+            // Check that the profiler is enabled
+            if ($profiler = $client->getProfiler()) {
+                // check the number of requests
+                $this->assertTrue($profiler->get('db')->getQueryCount() < 10);
+
+                // check the time spent in the framework
+                $this->assertTrue( $profiler->get('timer')->getTime() < 0.5);
+            }
+        }
     }
 
+If a test fails because of profiling data (too many DB queries for instance),
+you might want to use the Web Profiler to analyze the request after the tests
+finish. It's easy to achieve if you embed the token in the error message::
+
+    $this->assertTrue(
+        $profiler->get('db')->getQueryCount() < 30,
+        sprintf('Checks that query count is less than 30 (token %s)', $profiler->getToken())
+    );
+
+.. caution::
+
+     The profiler store can be different depending on the environment
+     (especially if you use the SQLite store, which is the default configured
+     one).
+
 .. note::
 
     The profiler information are available even if you insulate the client or
     if you use an HTTP layer for your tests.
+
+.. tip::
+
+    Read the API for built-in `data collectors`_ to learn more about their
+    interfaces.

guides/internals/profiler.rst

@@ -48,49 +48,6 @@ in development to debug your code and enhance performance; but it can also be
 used to explore problems that occur in production. It exposes all information
 collected by the profiler in a web interface.
 
-Using the Profiler in Functional Tests
---------------------------------------
-
-Profiling data are available in functional tests. It gives you a great way to
-check various things and enforce some metrics::
-
-    class HelloControllerTest extends WebTestCase
-    {
-        public function testIndex()
-        {
-            $client = $this->createClient();
-            $crawler = $client->request('GET', '/hello/Fabien');
-
-            // Write some assertions about the Response
-            // ...
-
-            // Check that the profiler is enabled
-            if ($profiler = $client->getProfiler()) {
-                $this->assertTrue($profiler->get('db')->getQueryCount() < 30);
-                $this->assertTrue($profiler->get('timer')->getTime() < 50);
-            }
-        }
-    }
-
-.. tip::
-
-    Read the API for built-in `data collectors`_ to learn more about their
-    interfaces.
-
-If a test fails because of profiling data (too many DB queries for instance),
-you might want to use the Web Profiler to analyze the request after the tests
-finish. It's easy to achieve if you embed the token in the error message::
-
-    $this->assertTrue(
-        $profiler->get('db')->getQueryCount() < 30,
-        sprintf('checks that query count is less than 30 (token %s)', $profiler->getToken())
-    );
-
-.. caution::
-
-     The profiler store can be different depending on the environment
-     (especially if you use the SQLite store, which is the default configured
-     one).
 
 Accessing the Profiling information
 -----------------------------------