You can use one of the following methods to send a request:. All of the methods except get and delete accept a second parameter that allows you to send a request body.
After dispatching a request you can use the various assertions provided by IntegrationTestTrait or PHPUnit to ensure your request had the correct side-effects. The IntegrationTestTrait trait comes with a number of helpers to to configure the requests you will send to your application under test:. The state set by these helper methods is reset in the tearDown method. You can use helper methods in IntegrationTestTrait to do this.
Assuming you had an ArticlesController that contained an add method, and that add method required authentication, you could write the following tests:.
To test APIs that use stateless authentication, such as Basic authentication, you can configure the request to inject environment conditions or headers that simulate actual authentication request headers. These environment variables used in the authentication adapter outlined in Using Basic Authentication :. If you are testing other forms of authentication, such as OAuth2, you can set the Authorization header directly:. The headers key in configRequest can be used to configure any additional HTTP headers needed for an action.
It is also important to enable debug in tests that use tokens to prevent the SecurityComponent from thinking the debug token is being used in a non-debug environment. When testing with other methods like requireSecure you can use configRequest to set the correct environment variables:. If your action requires unlocked fields you can declare them with setUnlockedFields :.
Integration testing can also be used to test your entire PSR-7 application and Middleware. You can customize the application class name used, and the constructor arguments, by using the configApplication method:. Alternatively if you wish to load plugins manually in a test you can use the loadPlugins method. If you use the Encrypted Cookie Middleware in your application, there are helper methods for setting encrypted cookies in your test cases:.
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:. 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:.
In order to simulate exactly how the uploaded file objects would be present on a regular request, you not only need to pass them in the request data, but you also need to pass them to the test request configuration via the files option.
If you configure the test request with files, then it must match the structure of your POST data but only include the uploaded file objects! Likewise you can simulate upload errors or otherwise invalid files that do not pass validation:. When debugging tests that are failing because your application is encountering errors it can be helpful to temporarily disable the error handling middleware to allow the underlying error to bubble up. You can use disableErrorHandlerMiddleware to do this:.
In the above example, the test would fail and the underlying exception message and stack trace would be displayed instead of the rendered error page being checked. The IntegrationTestTrait trait provides a number of assertion methods that make testing responses much simpler. Some examples are:. In addition to the above assertion methods, you can also use all of the assertions in TestSuite and those found in PHPUnit.
For some types of test, it may be easier to compare the result of a test to the contents of a file - for example, when testing the rendered output of a view. The StringCompareTrait adds a simple assert method for this purpose.
Usage involves using the trait, setting the comparison base path and calling assertSameAsFile :. See Testing Commands for how to test console commands. See Mocking Services in Tests for how to replace services injected with the dependency injection container in your integration tests.
Generally most applications will not directly test their HTML code. Doing so is often results in fragile, difficult to maintain test suites that are prone to breaking. This component helps us set the pagination limit value across all the controllers that use it.
Now we can write tests to ensure our paginate limit parameter is being set correctly by the adjust method in our component. First we create an example helper to test. The CurrencyRendererHelper will help us display currencies in our views and for simplicity only has one method usd :. Here, we call usd with different parameters and tell the test suite to check if the returned values are equal to what is expected.
Save this and execute the test. You should see a green bar and messaging indicating 1 pass and 4 assertions. When you are testing a Helper which uses other helpers, be sure to mock the View clases loadHelpers method. The Events System is a great way to decouple your application code, but sometimes when testing, you tend to test the results of events in the test cases that execute those events. This is an additional form of coupling that can be removed by using assertEventFired and assertEventFiredWith instead.
To assert that events are fired, you must first enable Tracking Events on the event manager you wish to assert against. By default, the global EventManager is used for assertions, so testing global events does not require passing the event manager:. See Testing Mailers for information on testing email. If you want several of your tests to run at the same time, you can create a test suite.
A test suite is composed of several test cases. A simple example would be:. They work just like normal tests but you have to remember to use the naming conventions for plugins when importing classes. This is an example of a testcase for the BlogPost model from the plugins chapter of this manual. You also need to prefix your plugin fixtures with plugin. BlogPosts :. If you want to use plugin fixtures in the app tests you can reference them using plugin. Additionally if you use vendor plugin name or fixture directories you can use the following: plugin.
Before you can use fixtures you should ensure you have the fixture listener configured in your phpunit. You should also ensure that your fixtures are loadable.
Ensure the following is present in your composer. Remember to run composer. My Scala 3 SimpleTest source code mini testing framework.
Scala - calling foreach on a Seq to populate sample data. Scala 3 opaque types: How to create meaningful type names. Scala 3 modules: How to build modular systems. Docker cheat sheet cheatsheet. You can follow any responses to this entry through the RSS 2. You can leave a response , or trackback from your own site.
The following software should be installed and an initial design of the database schema created using MySQL […]. You are commenting using your WordPress. You are commenting using your Google account.
You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email.
0コメント