-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Add docs for testing flash messages. #4971
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1075,6 +1075,92 @@ events/routes are connected for each test case. | |
| .. versionadded:: 3.3.0 | ||
| PSR-7 Middleware and the ``useHttpServer()`` method were added in 3.3.0. | ||
|
|
||
| Testing with Encrypted Cookies | ||
| ------------------------------ | ||
|
|
||
| If you use the :php:class:`Cake\\Controller\\Component\\CookieComponent` in your | ||
| controllers, your cookies are likely encrypted. As of 3.1.7, CakePHP provides | ||
| helper methods for interacting with encrypted cookies in your test cases:: | ||
|
|
||
| // Set a cookie using AES and the default key. | ||
| $this->cookieEncrypted('my_cookie', 'Some secret values'); | ||
|
|
||
| // Assume this action modifies the cookie. | ||
| $this->get('/bookmarks/index'); | ||
|
|
||
| $this->assertCookieEncrypted('An updated value', 'my_cookie'); | ||
|
|
||
| .. versionadded: 3.1.7 | ||
| ``assertCookieEncrypted`` and ``cookieEncrypted`` were added in 3.1.7. | ||
|
|
||
| Testing Flash Messages | ||
| ---------------------- | ||
|
|
||
| If you want to assert the presence of flash messages in the session and not the | ||
| rendered HTML, you can use ``enableRetainFlashMessages()`` in your tests to | ||
| retain flash messages in the session so you can write assertions:: | ||
|
|
||
| $this->enableRetainFlashMessages(); | ||
| $this->get('/bookmarks/delete/9999'); | ||
|
|
||
| $this->assertSession('That bookmark does not exist', 'Flash.flash.0.message'); | ||
|
|
||
| .. versionadded:: 3.4.7 | ||
| ``enableRetainFlashMessages()`` was added in 3.4.7 | ||
|
|
||
| Testing a JSON Responding Controller | ||
| ------------------------------------ | ||
|
|
||
| JSON is a friendly and common format to use when building a web service. | ||
| Testing the endpoints of your web service is very simple with CakePHP. Let us | ||
| begin with a simple example controller that responds in JSON:: | ||
|
|
||
| class MarkersController extends AppController | ||
| { | ||
| public function initialize() | ||
| { | ||
| parent::initialize(); | ||
| $this->loadComponent('RequestHandler'); | ||
| } | ||
|
|
||
| public function view($id) | ||
| { | ||
| $marker = $this->Markers->get($id); | ||
| $this->set([ | ||
| '_serialize' => ['marker'], | ||
| 'marker' => $marker, | ||
| ]); | ||
| } | ||
| } | ||
|
|
||
| Now we create the file **tests/TestCase/Controller/MarkersControllerTest.php** | ||
| and make sure our web service is returning the proper response:: | ||
|
|
||
| class MarkersControllerTest extends IntegrationTestCase | ||
| { | ||
|
|
||
| public function testGet() | ||
| { | ||
| $this->configRequest([ | ||
| 'headers' => ['Accept' => 'application/json'] | ||
| ]); | ||
| $result = $this->get('/markers/view/1.json'); | ||
|
|
||
| // Check that the response was a 200 | ||
| $this->assertResponseOk(); | ||
|
|
||
| $expected = [ | ||
| ['id' => 1, 'lng' => 66, 'lat' => 45], | ||
| ]; | ||
| $expected = json_encode($expected, JSON_PRETTY_PRINT); | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Isn't there an assertion taht does JSON encoding already? |
||
| $this->assertEquals($expected, $this->_response->body()); | ||
| } | ||
| } | ||
|
|
||
| We use the ``JSON_PRETTY_PRINT`` option as CakePHP's built in JsonView will use | ||
| that option when ``debug`` is enabled. | ||
|
|
||
|
|
||
| Assertion methods | ||
| ----------------- | ||
|
|
||
|
|
@@ -1201,76 +1287,6 @@ comparison files as they are referenced: | |
| # | ||
| # modified: tests/comparisons/example.php | ||
|
|
||
| Testing with Encrypted Cookies | ||
| ------------------------------ | ||
|
|
||
| If you use the :php:class:`Cake\\Controller\\Component\\CookieComponent` in your | ||
| controllers, your cookies are likely encrypted. As of 3.1.7, CakePHP provides | ||
| helper methods for interacting with encrypted cookies in your test cases:: | ||
|
|
||
| // Set a cookie using aes and the default key. | ||
| $this->cookieEncrypted('my_cookie', 'Some secret values'); | ||
|
|
||
| // Assume this action modifies the cookie. | ||
| $this->get('/bookmarks/index'); | ||
|
|
||
| $this->assertCookieEncrypted('An updated value', 'my_cookie'); | ||
|
|
||
| .. versionadded: 3.1.7 | ||
| ``assertCookieEncrypted`` and ``cookieEncrypted`` were added in 3.1.7. | ||
|
|
||
| Testing a JSON Responding Controller | ||
| ------------------------------------ | ||
|
|
||
| JSON is a friendly and common format to use when building a web service. | ||
| Testing the endpoints of your web service is very simple with CakePHP. Let us | ||
| begin with a simple example controller that responds in JSON:: | ||
|
|
||
| class MarkersController extends AppController | ||
| { | ||
| public function initialize() | ||
| { | ||
| parent::initialize(); | ||
| $this->loadComponent('RequestHandler'); | ||
| } | ||
|
|
||
| public function view($id) | ||
| { | ||
| $marker = $this->Markers->get($id); | ||
| $this->set([ | ||
| '_serialize' => ['marker'], | ||
| 'marker' => $marker, | ||
| ]); | ||
| } | ||
| } | ||
|
|
||
| Now we create the file **tests/TestCase/Controller/MarkersControllerTest.php** | ||
| and make sure our web service is returning the proper response:: | ||
|
|
||
| class MarkersControllerTest extends IntegrationTestCase | ||
| { | ||
|
|
||
| public function testGet() | ||
| { | ||
| $this->configRequest([ | ||
| 'headers' => ['Accept' => 'application/json'] | ||
| ]); | ||
| $result = $this->get('/markers/view/1.json'); | ||
|
|
||
| // Check that the response was a 200 | ||
| $this->assertResponseOk(); | ||
|
|
||
| $expected = [ | ||
| ['id' => 1, 'lng' => 66, 'lat' => 45], | ||
| ]; | ||
| $expected = json_encode($expected, JSON_PRETTY_PRINT); | ||
| $this->assertEquals($expected, $this->_response->body()); | ||
| } | ||
| } | ||
|
|
||
| We use the ``JSON_PRETTY_PRINT`` option as CakePHP's built in JsonView will use | ||
| that option when ``debug`` is enabled. | ||
|
|
||
| Testing Views | ||
| ============= | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this could be quite common, I presume, couldn't we have a
setAcceptsJson()or something like that?