Symfony Live San Franciso 2017 - BDD API Development with Symfony and Behat
•
0 likes•253 views
BDD API Development with Symfony and Behat You may have built an API in Symfony before. You may have even written some browser tests in Beta. Did you ever consider using Behat to write integration tests for your API? If not, you definitely should. The portability and reusability of Behat steps make it the perfect platform for API integration tests. The Symfony kernel integration for Behat and absence of JavaScript in an API makes this match made in heaven. Pull up a cloud and let me show you the pure awesomeness that is BDD API Development with Symfony and Behat.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Symfony Live San Franciso 2017 - BDD API Development with Symfony and Behat
Similar to Symfony Live San Franciso 2017 - BDD API Development with Symfony and Behat (20)
More from Adam Englander
More from Adam Englander (20)
Recently uploaded
Recently uploaded (20)
Symfony Live San Franciso 2017 - BDD API Development with Symfony and Behat
- 1. @adam_englander BDD API Development with Symfony and Behat Adam Englander LaunchKey Architect, iovation
- 3. @adam_englander APIs are taking over!
- 13. @adam_englander Your Application Bundle Routing Serializer
- 14. @adam_englander Your Application Bundle Routing Firewall Serializer
- 15. @adam_englander Your Application Bundle Routing Firewall Serializer Cache
- 16. @adam_englander Your Application Bundle Routing Firewall Serializer Event Dispatcher Cache
- 17. @adam_englander Your Application Bundle Routing Firewall Serializer Event Dispatcher Dependency Cache
- 18. @adam_englander Your Application Bundle Routing Firewall Serializer Event Dispatcher Config Dependency Cache
- 19. @adam_englander Your Application Bundle Routing Firewall Serializer Event Dispatcher Config TranslationDependency Cache
- 20. @adam_englander Your Application Bundle Routing Firewall Serializer Event Dispatcher Config App Kernels TranslationDependency Cache
- 21. @adam_englander Your Application Bundle Routing Firewall Serializer Event Dispatcher Config App Kernels TranslationDependency Cache Full Integration Testing Required
- 25. @adam_englander Behavior Driven Development is for websites!
- 26. @adam_englander Behavior is Behavior Web Mobile Device to Device
- 27. @adam_englander Actor 1 Acts -> Actor 2 Responds Show the homepage Here is the homepage Adam is home I turned on the lights
- 28. @adam_englander Instead of dealing with this:
- 29. @adam_englander Well, actually, this: <!DOCTYPE html> <head> <title>Symfony</title> </head> <body> <div class="position-relative js-header-wrapper"> <a href="#start" tabindex="1" class=“bg-black"> Skip to content </a> <div id="loader-bar" class=“pjax-loader-bar”> <div class=“progress"></div> </div> . . .
- 30. @adam_englander You are dealing with this: HTTP/1.1 200 OK Date: Thu, 19 Oct 2017 06:28:02 GMT Content-Type: application/json; charset=utf-8 Content-Length: 1009 Server: GitHub.com Status: 200 OK Vary: Accept-Encoding X-GitHub-Request-Id: CD6C:D7DE:E24F3B2:123F37BB:59E845F1 { "login": "symfony", "id": 143937, "url": "https://api.github.com/orgs/symfony", . . .
- 31. @adam_englander Feature: All pages require login As a user In order to view the home page I must login to the website Scenario: Not logged in redirects to login page When I go to the home page Then I am redirected to the login page Scenario: Logged sees page Given I am logged in When I go to the home page Then I see hello Adam Web
- 32. @adam_englander Feature: All endpoints require OAuth token As an API consumer In order to access an endpoint I must be authenticated Scenario: Not logged in shows 401 When I access the status endpoint Then the HTTPS Status is 401 Unauthorized And the WWW-Authenticate header is Bearer realm=“API Realm” Scenario: Authorized returns endpoint response Given a valid OAuth Token When I access the status endpoint Then the HTTP Status is 200 OK Device to Device
- 33. @adam_englander That’s nice and all. How do I do Kernel and Live tests?
- 35. @adam_englander Default Profile: Symfony Extension default: extensions: BehatSymfony2Extension: ~ suites: default: contexts: [SymfonyKernelFeatureContext]
- 36. @adam_englander Server Profile: Guzzle Client server: extensions: [] suites: default: contexts: - GuzzleFeatureContext: - base_uri: http://localhost:8000
- 38. @adam_englander Abstract Context protected abstract function sendRequestImpl( RequestInterface $request): ResponseInterface; /** * @Then /^the response status code is (d+)$/ */ public function theResponseStatusCodeIs($statusCode) { MatcherAssert::assertThat( $this->response->getStatusCode(), Matchers::equalTo($statusCode) ); }
- 39. @adam_englander Guzzle Client Context "require-dev": { "guzzlehttp/guzzle": “^6.3”, . . .
- 40. @adam_englander Guzzle Client Context public function __construct($config) { $this->client = new GuzzleHttpClient($config); }
- 41. @adam_englander Guzzle Client Context protected function sendRequestImpl($request) { try { $response = $this->client->send($request); } catch (ClientException $clientException) { $response = $clientException->getResponse(); } return $response; }
- 42. @adam_englander Symfony Kernel Context "require-dev": { "behat/symfony2-extension": “^2.1.1", "symfony/psr-http-message-bridge": "^1.0", "zendframework/zend-diactoros": "^1.4" . . . }
- 43. @adam_englander Symfony Kernel Context class SymfonyKernelFeatureContext extends AbstractFeatureContext implements KernelAwareContext public function __construct() { $this->psr7Factory = new DiactorosFactory(); } public function setKernel(KernelInterface $kernel) { $this->client = $kernel ->getContainer()->get(‘test.client'); }
- 44. @adam_englander Symfony Kernel Context protected function sendRequestImpl($request) { $this->client->request( $request->getMethod(), $request->getUri()->getPath()); $clientResponse = $this->client->getResponse(); $response = $this->psr7Factory ->createResponse($clientResponse); return $response; }
- 46. @adam_englander Lessons From the Trenches
- 47. @adam_englander LaunchKey MFA API 41 Unique paths 130 handler methods ~10K lines of code 120 libraries
- 48. @adam_englander LaunchKey MFA API Tests 55 Features 328 Scenarios ~3K lines of step code
- 49. @adam_englander Split feature files by functional features not by path.
- 50. @adam_englander Break functionality into multiple contexts like you would bundles.
- 51. @adam_englander If you have complex step code, unit test that code!
- 52. @adam_englander Expose endpoints for setup and teardown.
- 53. @adam_englander Test a feature only once. Every step that is not testing the feature is a Given.
- 54. @adam_englander Every Given needs to be tested in another Feature.