Skip to content

Commit 3e444b0

Browse files
author
Davert
committed
=auto-updated documentation
1 parent a6e8334 commit 3e444b0

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/05-FunctionalTests.markdown

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -156,20 +156,20 @@ modules:
156156

157157
[See the full reference](http://codeception.com/docs/modules/Symfony1)
158158

159-
## Integrating Unsupported Frameworks
159+
## Integrating Other Frameworks
160160

161161
Codeception doesn't provide any generic functional testing module because there are a lot of details we can't implement in general.
162162
We already discussed the common pitfalls for functional testing. And there is no one single recipe how to solve them for all PHP applications.
163163
So if you don't use any of the frameworks listed above, you might want to integrate your framework into Codeception. That task requires some knowledge of Codeception internals and some time. Probably, you are ok with just acceptance tests, but any help in extending Codeception functionality will be appreciated. We will review what should be done to have your framework integrated.
164164

165-
### HttpKernel Framework
165+
#### With HttpKernel
166166

167167
If you have a framework that uses Symfony's `HttpKernel`, using it with Codeception will be like a piece of cake.
168168
You will need to create a module for it and test it on your application.
169169
We already have a [guide for such integration](http://codeception.com/01-24-2013/connecting-php-frameworks-1.html).
170170
Develop a module, try it and share with community.
171171

172-
### Other Frameworks
172+
#### Any Other
173173

174174
Integration is a bit harder if your framework is not using HttpKernel component.
175175
The hardest part of it is resolving commong pitfalls: memory management, and usage of `headers` function.

0 commit comments

Comments
 (0)