everycheck/test-api-rest-bundle

This package is abandoned and no longer maintained. No replacement package was suggested.

Allows you to easily test a rest api

1.4.0 2022-01-20 15:12 UTC

Requires

• coduo/php-matcher: ^3.0
• jms/serializer-bundle: ^1.0|^2.0
• phpunit/phpunit: ^6.0|^7.0
• symfony/phpunit-bridge: ^3.0

Requires (Dev)

• doctrine/doctrine-bundle: ^1.11
• doctrine/orm: ^2.6
• guzzlehttp/guzzle: ^6.3
• ramsey/uuid-doctrine: ^1.5
• sensio/distribution-bundle: ^5.0
• sensio/framework-extra-bundle: ^5.0.0
• symfony/monolog-bundle: ^3.1
• symfony/polyfill-apcu: ^1.0
• symfony/swiftmailer-bundle: ^3.2
• symfony/symfony: 3.4.*
• symfony/web-server-bundle: ^3.4

MIT

• rest
• api
• test

README

About

TestApiRestBundle allows you to test your Symfony REST API deeply. It checks the validity of your application and ensures it stays robust throughout time using PHPUnit and via unit, scenario and database testing.

Table of contents

• About
• Installation
• Configuration
• Usages
• Tests folder structure
• Launching test

Installation

You can install using composer, assuming it's already installed globally :

composer require --dev everycheck\test-api-rest-bundle

Configuration

Configure the relative paths of the directories containing the requests payloads that you would send in your tests and their expected responses. The paths are taken from AcmeBundle\tests\AcmeBundle.

test_api_rest:
    directory:
        payloads: path/to/payloads
        responses: path/to/responses

So, here, the real path of the directories are :

AcmeBundle\tests\AcmeBundle\path\to\payloads AcmeBundle\tests\AcmeBundle\path\to\responses

Usages

• Basic usages

Advanced usages

• Test dynamic responses
• Reuse response content
• Test email sending and their content

Tests folder structure

To test one of your bundle, you just have to replicate the structure of that one and add some directories by the following structure

.
├── tests                                       #   The basic Symfony test directory
│   ├── AcmeFooBundle                           #   Name of your bundle
│   │   ├── Controller                          
│   │   │   ├── FooControllerTest.php           #   Controller your want to test
│   │   │   └── ...                                    
│   │   │
│   │   ├── DataFixtures                        
│   │   │   └── ORM                             
│   │   │       ├─ LoadAcmeFooFixtures.php     #   Fixtures dedicated to one controller   
|   |   |       └── ...
│   │   │                                       
│   │   ├── Payloads                            
│   │   │   └── ...                             #   File posted to your API
│   │   │                                       
│   │   ├── Resources                           
│   │   │   └── config                          
│   │   │       ├── foo.yaml                    #   All the tests for a specific controller, set as a YAML file
│   │   │       └── ...                    
│   │   │   
│   │   └── Responses                           #   All the expected responses coming from the endpoints of your API when testing it
│   │       └── Expected
│   │           └── ...
│   └──
└──

Launching test

Here are the commands to execute in order to test the bundle :

composer install

./Tests/sampleProject/app/console d:d:d --force
./Tests/sampleProject/app/console d:d:c
./Tests/sampleProject/app/console d:s:c
./Tests/sampleProject/app/console s:start --docroot=./Tests/sampleProject/public

php ./Tests/sampleProject/tests/DemoBundle/DataFixtures/LoadDemoFixture.php localhost:portYouAreListening "[debug]"
php ./Tests/sampleProject/tests/PatternBundle/DataFixtures/LoadPatternFixture.php localhost:portYouAreListening "[debug]"

./Tests/sampleProject/app/console s:stop

./vendor/bin/phpunit