debug

Author: abluchet

.travis.yml

@@ -49,7 +49,7 @@ install:
 
 script:
   - if [[ $coverage = 1 ]]; then phpdbg -qrr vendor/bin/phpunit --coverage-php build/cov/coverage-phpunit.cov; else vendor/bin/phpunit; fi
-  - if [[ $coverage = 1 ]]; then for f in $(find features -name '*.feature'); do FEATURE=${f//\//_} phpdbg -qrr vendor/bin/behat --format=progress --profile coverage $f || exit $?; done; else vendor/bin/behat --format=progress; fi
+  - if [[ $coverage = 1 ]]; then for f in $(find features -name '*.feature'); do FEATURE=${f//\//_} phpdbg -qrr vendor/bin/behat --format=progress --profile coverage $f || exit $?; done; elif [[ $postgres = 1 ]]; then vendor/bin/behat --stop-on-failure; else vendor/bin/behat --format=progress; fi
   - if [[ $coverage = 1 ]]; then phpdbg -qrr phpcov.phar merge --clover build/logs/clover.xml build/cov; fi
   - tests/Fixtures/app/console api:swagger:export > swagger.json && swagger validate swagger.json && rm swagger.json
   - if [[ $lint = 1 ]]; then php php-cs-fixer.phar fix --dry-run --diff --no-ansi; fi

behat.yml.dist

@@ -3,12 +3,12 @@ default:
     default:
       contexts:
         - 'FeatureContext': { doctrine: '@doctrine' }
+        - 'JsonContext'
         - 'HydraContext'
         - 'SwaggerContext'
         - 'HttpCacheContext'
         - 'Behat\MinkExtension\Context\MinkContext'
         - 'Behatch\Context\RestContext'
-        - 'Behatch\Context\JsonContext'
   extensions:
     'Behat\Symfony2Extension':
       kernel:

features/bootstrap/JsonContext.php

@@ -0,0 +1,62 @@
+<?php
+
+/*
+ * This file is part of the API Platform project.
+ *
+ * (c) Kévin Dunglas <[email protected]>
+ *
+ * For the full copyright and license information, please view the LICENSE
+ * file that was distributed with this source code.
+ */
+
+declare(strict_types=1);
+
+use Behat\Gherkin\Node\PyStringNode;
+use Behatch\Context\JsonContext as BaseJsonContext;
+use Behatch\HttpCall\HttpCallResultPool;
+use Behatch\Json\Json;
+
+final class JsonContext extends BaseJsonContext
+{
+    public function __construct(HttpCallResultPool $httpCallResultPool)
+    {
+        parent::__construct($httpCallResultPool);
+    }
+
+    private function sortArrays(&$obj) {
+        foreach ($obj as $key => &$value) {
+            if (is_scalar($value)) {
+                continue;
+            }
+
+            if (is_array($value)) {
+                sort($value);
+            }
+
+            $this->sortArrays($value);
+        }
+    }
+
+    /**
+     * @Then /^the JSON should be deep equal to:$/
+     */
+    public function theJsonShouldBeDeepEqualTo(PyStringNode $content)
+    {
+        $actual = $this->getJson();
+        try {
+            $expected = new Json($content);
+        }
+        catch (\Exception $e) {
+            throw new \Exception('The expected JSON is not a valid');
+        }
+
+        $this->sortArrays($actual->getContent());
+        $this->sortArrays($expected->getContent());
+
+        $this->assertSame(
+            (string) $expected,
+            (string) $actual,
+            "The json is equal to:\n". $actual->encode()
+        );
+    }
+}

features/doctrine/numeric_filter.feature

@@ -7,7 +7,8 @@ Feature: Numeric filter on collections
   Scenario: Get collection by id equals 9.99 which is not possible
     Given there is "30" dummy objects
     When I send a "GET" request to "/dummies?id=9.99"
-    Then the response status code should be 200
+    Then print last JSON response
+    And the response status code should be 200
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
     And the JSON should be valid according to this schema:

features/doctrine/search_filter.feature

@@ -18,8 +18,8 @@ Feature: Search filter on collections
   Scenario: Test #944
     Given there is a DummyCar entity with related colors
     When I send a "GET" request to "/dummy_cars?colors.prop=red"
-    Then the response status code should be 200
-    And the JSON should be equal to:
+    And the response status code should be 200
+    And the JSON should be deep equal to:
 		"""
     {
         "@context": "/contexts/DummyCar",
@@ -213,7 +213,8 @@ Feature: Search filter on collections
 
   Scenario: Search collection by description (word_start)
     When I send a "GET" request to "/dummies?description=smart"
-    Then the response status code should be 200
+    Then print last JSON response
+    And the response status code should be 200
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
     And the JSON should be valid according to this schema:

features/integration/fos_user.feature

@@ -15,7 +15,8 @@ Feature: FOSUser integration
       "plainPassword": "azerty"
     }
     """
-    Then the response status code should be 201
+    Then print last JSON response
+    And the response status code should be 201
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
     And the JSON should be equal to:

features/main/composite.feature

@@ -11,7 +11,7 @@ Feature: Retrieve data with Composite identifiers
     Then the response status code should be 200
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
-    And the JSON should be equal to:
+    And the JSON should be deep equal to:
     """
     {
       "@context": "/contexts/CompositeItem",

features/main/uuid.feature

@@ -10,25 +10,25 @@ Feature: Using uuid identifier on resource
     """
     {
       "name": "My Dummy",
-      "uuid": "41B29566-144B-11E6-A148-3E1D05DEFE78"
+      "uuid": "41b29566-144b-11e6-a148-3e1d05defe78"
     }
     """
     Then the response status code should be 201
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
 
   Scenario: Get a resource
-    When I send a "GET" request to "/uuid_identifier_dummies/41B29566-144B-11E6-A148-3E1D05DEFE78"
+    When I send a "GET" request to "/uuid_identifier_dummies/41b29566-144b-11e6-a148-3e1d05defe78"
     Then the response status code should be 200
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
     And the JSON should be equal to:
     """
     {
       "@context": "/contexts/UuidIdentifierDummy",
-      "@id": "/uuid_identifier_dummies/41B29566-144B-11E6-A148-3E1D05DEFE78",
+      "@id": "/uuid_identifier_dummies/41b29566-144b-11e6-a148-3e1d05defe78",
       "@type": "UuidIdentifierDummy",
-      "uuid": "41B29566-144B-11E6-A148-3E1D05DEFE78",
+      "uuid": "41b29566-144b-11e6-a148-3e1d05defe78",
       "name": "My Dummy"
     }
     """
@@ -46,9 +46,9 @@ Feature: Using uuid identifier on resource
       "@type": "hydra:Collection",
       "hydra:member": [
           {
-              "@id": "/uuid_identifier_dummies/41B29566-144B-11E6-A148-3E1D05DEFE78",
+              "@id": "/uuid_identifier_dummies/41b29566-144b-11e6-a148-3e1d05defe78",
               "@type": "UuidIdentifierDummy",
-              "uuid": "41B29566-144B-11E6-A148-3E1D05DEFE78",
+              "uuid": "41b29566-144b-11e6-a148-3e1d05defe78",
               "name": "My Dummy"
           }
       ],
@@ -58,7 +58,7 @@ Feature: Using uuid identifier on resource
 
   Scenario: Update a resource
     When I add "Content-Type" header equal to "application/ld+json"
-    And I send a "PUT" request to "/uuid_identifier_dummies/41B29566-144B-11E6-A148-3E1D05DEFE78" with body:
+    And I send a "PUT" request to "/uuid_identifier_dummies/41b29566-144b-11e6-a148-3e1d05defe78" with body:
     """
     {
       "name": "My Dummy modified"
@@ -71,9 +71,9 @@ Feature: Using uuid identifier on resource
     """
     {
       "@context": "/contexts/UuidIdentifierDummy",
-      "@id": "/uuid_identifier_dummies/41B29566-144B-11E6-A148-3E1D05DEFE78",
+      "@id": "/uuid_identifier_dummies/41b29566-144b-11e6-a148-3e1d05defe78",
       "@type": "UuidIdentifierDummy",
-      "uuid": "41B29566-144B-11E6-A148-3E1D05DEFE78",
+      "uuid": "41b29566-144b-11e6-a148-3e1d05defe78",
       "name": "My Dummy modified"
     }
     """
@@ -99,6 +99,6 @@ Feature: Using uuid identifier on resource
 
   @dropSchema
   Scenario: Delete a resource
-    When I send a "DELETE" request to "/uuid_identifier_dummies/41B29566-144B-11E6-A148-3E1D05DEFE78"
+    When I send a "DELETE" request to "/uuid_identifier_dummies/41b29566-144b-11e6-a148-3e1d05defe78"
     Then the response status code should be 204
     And the response should be empty