Gintautas Miselis

All you gave here is a single line description in subject. It isn't a useful bug report or even support request. Please provide exact information about how your tests are...

Have you got `database.default` setting in your Laravel configuration?

Please run codeception with `-vv` parameter and check if you see the following lines in the output: ``` [Database] Transaction started ``` ``` [Database] Transaction cancelled; all changes reverted. ```

Laravel module starts transaction before each test and rolls it back after each test. This may cause issues if your application is using its own transactions. If you don't want...

> Why does unit test requires a database connection actually we dont run any test directly on a db. Because Laravel module is enabled, do you really need it in...

`suite.start`, `suite.end`, `test.parsed` events are not internal, because they aren't use anywhere, we, probably, can delete them. step events are used.

I messed up merging your branch a little bit, so your change can be found in this commit: https://github.com/Codeception/Codeception/commit/db01ddac045df4aa53b2d9de6e55c8d1f4c31053

Was it really a problem with PhpBrowser? I doubt that it can send null value over HTTP.

Fields listed twice certainly looks like a bug. submitButton in the form array is probably Symfony specific. Button parameter not only uses value of the button, but also checks `formaction`...

I noticed the same issue in Symfony tests and wrote about it in #6348 @mdoelker What do you think about restoring original behaviour?