debug2

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; elif [[ $postgres = 1 ]]; then vendor/bin/behat --stop-on-failure; 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 --tags ~@postgres --format=progress --profile coverage $f || exit $?; done; elif [[ $postgres = 1 ]]; then vendor/bin/behat --tags ~@sqlite --stop-on-failure; else vendor/bin/behat --tags ~@postgres --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

features/doctrine/numeric_filter.feature

@@ -1,3 +1,13 @@
+# None of these tests have something to do with the numeric filter
+# indeed they're only testing searchFilter with numeric values
+# the only numeric filters are on properties dummyFloat and dummyPrice
+# and none of the above is tested in this file
+# Testing on postgresql made searching `id=9.99` bug since `id` is an integer
+# @TODO move this stuff to search fitler + do numeric tests
+# @TODO remove the sqlite tag by:
+#   - skipping incorrect search filters on numeric database types?
+#   - fixing that $field === 'id' stuff in SearchFilter? (since when `id` is always the index key)
+@sqlite
 Feature: Numeric filter on collections
   In order to retrieve ordered large collections of resources
   As a client software developer
@@ -7,7 +17,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:
@@ -35,7 +46,8 @@ Feature: Numeric filter on collections
 
   Scenario: Get collection by id 10
     When I send a "GET" request to "/dummies?id=10"
-    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

@@ -211,6 +211,7 @@ Feature: Search filter on collections
     }
     """
 
+  @sqlite
   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
@@ -250,6 +251,47 @@ Feature: Search filter on collections
     }
     """
 
+  # note on Postgres compared to sqlite the LIKE clause is case sensitive
+  @postgres
+  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
+    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:
+    """
+    {
+      "type": "object",
+      "properties": {
+        "@context": {"pattern": "^/contexts/Dummy$"},
+        "@id": {"pattern": "^/dummies$"},
+        "@type": {"pattern": "^hydra:Collection$"},
+        "hydra:member": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "@id": {
+                "oneOf": [
+                  {"pattern": "^/dummies/2$"},
+                  {"pattern": "^/dummies/4$"},
+                  {"pattern": "^/dummies/6$"}
+                ]
+              }
+            }
+          }
+        },
+        "hydra:view": {
+          "type": "object",
+          "properties": {
+            "@id": {"pattern": "^/dummies\\?description=smart"},
+            "@type": {"pattern": "^hydra:PartialCollectionView$"}
+          }
+        }
+      }
+    }
+    """
+
   @dropSchema
   Scenario: Search for entities within an impossible range
     When I send a "GET" request to "/dummies?name=MuYm"

features/http_cache/tags.feature

@@ -1,3 +1,4 @@
+@sqlite
 Feature: Cache invalidation through HTTP Cache tags
   In order to have a fast API
   As an API software developer

features/integration/fos_user.feature

@@ -15,8 +15,7 @@ Feature: FOSUser integration
       "plainPassword": "azerty"
     }
     """
-    Then print last JSON response
-    And the response status code should be 201
+    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"
     And the JSON should be equal to:

tests/Fixtures/TestBundle/Entity/User.php

@@ -23,6 +23,7 @@
  * A User.
  *
  * @ORM\Entity
+ * @ORM\Table(name="user_test")
  * @ApiResource(attributes={
  *     "normalization_context"={"groups"={"user", "user-read"}},
  *     "denormalization_context"={"groups"={"user", "user-write"}}

tests/Fixtures/app/config/config.yml

@@ -30,7 +30,7 @@ doctrine:
                 driver:   'pdo_pgsql'
                 dbname:   'api_platform_test'
                 user:     'postgres'
-                password: ''
+                password: 'api-platform'
                 host:     'localhost'
 
     orm: