Hi, Fabien > But when it comes to testing, things are much more complex. Because the > templating needs a loader, helpers, and some more services. So, > re-creating the dependency graph (with mock objects or not) is a more > difficult. At this point, you will probably just use the container in > your test to create the dependencies automatically (with a special > configuration for the test environment of course).
I am not sure I am following you. If you wanted to unit test the action, you would inject a mocked template. You don't need to mock its dependencies. If you want to do functional (end-to-end) testing, you'll have to provide the dependencies, either by hand or using a container. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en To unsubscribe from this group, send email to symfony-devs+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
