Version 1.2.1 (#8)

* Support new testbench for Laravel 7

* Update readme

* Test with Laravel 7

* Use trait method to create TestResponse

* Update changelog

* Update readme

Author: jenky

.github/workflows/testing.yml

@@ -11,17 +11,21 @@ jobs:
       fail-fast: true
       matrix:
         php: [7.1, 7.2, 7.3, 7.4]
-        laravel: [5.7.*, 5.8.*, 6.*]
+        laravel: [5.7.*, 5.8.*, 6.*, 7.*]
         include:
-            - laravel: 6.*
-              testbench: 4.*
-            - laravel: 5.8.*
-              testbench: 3.8.*
-            - laravel: 5.7.*
-              testbench: 3.7.*
+          - laravel: 7.*
+            testbench: 5.*
+          - laravel: 6.*
+            testbench: 4.*
+          - laravel: 5.8.*
+            testbench: 3.8.*
+          - laravel: 5.7.*
+            testbench: 3.7.*
         exclude:
-            - laravel: 6.*
-              php: 7.1
+          - laravel: 6.*
+            php: 7.1
+          - laravel: 7.*
+            php: 7.1
 
     name: PHP ${{ matrix.php }} / Laravel ${{ matrix.laravel }}
 
@@ -45,6 +49,6 @@ jobs:
         run: |
           composer require "laravel/framework:${{ matrix.laravel }}" "orchestra/testbench:${{ matrix.testbench }}" --no-interaction --no-update
           composer update --prefer-dist --no-interaction --no-suggest
-          
+
       - name: Execute tests
         run: vendor/bin/phpunit

.travis.yml

@@ -26,8 +26,6 @@ matrix:
       env: LARAVEL=^6.0
     - php: 7.1
       env: LARAVEL=^7.0
-  allow_failures:
-    - env: LARAVEL=^7.0
 
 before_script:
   - travis_retry composer update ${COMPOSER_FLAGS} --no-interaction --prefer-dist

CHANGELOG.md

@@ -16,6 +16,11 @@ Updates should follow the [Keep a CHANGELOG](http://keepachangelog.com/) princip
 
 ### Fixed -->
 
+## [1.2.1](https://github.com/jenky/hermes/compare/1.2.0...1.2.1) - 2020-03-03
+
+### Fixed
+- Fix test cases for Laravel 7.
+
 ## [1.2.0](https://github.com/jenky/hermes/compare/1.1.1...1.2.0) - 2020-02-28
 
 ### Added

README.md

@@ -122,6 +122,8 @@ If your middleware use Laravel service container binding implementations such as
 ],
 ```
 
+> An alternative way is [customizing the guzzle handler stack](#configure-the-guzzle-handler).
+
 ### Customizing the guzzle handler stack
 
 Sometimes you may need complete control over how guzzle's [HandleStack](http://docs.guzzlephp.org/en/stable/handlers-and-middleware.html#handlerstack) is configured for an existing channel. For example, you may want to add, remove or unshift a middleware for a given channel's handler stack.

composer.json

@@ -29,7 +29,7 @@
         "illuminate/container": "^5.7|^6.0|^7.0"
     },
     "require-dev": {
-        "orchestra/testbench": "^3.5|^4.0",
+        "orchestra/testbench": "^3.5|^4.0|^5.0",
         "phpunit/phpunit": "^7.0|^8.0",
         "squizlabs/php_codesniffer": "^3.0"
     },

tests/ResponseTest.php

@@ -2,7 +2,6 @@
 
 namespace Jenky\Hermes\Test;
 
-use Illuminate\Foundation\Testing\TestResponse;
 use Illuminate\Http\JsonResponse;
 use Jenky\Hermes\Response;
 
@@ -23,7 +22,7 @@ public function test_json_response()
         $response['exception'] = false;
         $this->assertFalse($response['exception']);
 
-        TestResponse::fromBaseResponse(
+        $this->createTestResponse(
             new JsonResponse($response->toArray(), $response->getStatusCode(), $response->header())
         )
             ->assertHeader('Content-Type', 'application/json')