@fkupper It seems you forgot a use statement in your PR in module-laravel, just like here. I fixed it with Codeception/module-laravel#27 .

I changed another assertEquals to assertSame b603cc2.

Finally, i ran these tests locally (on Windows) and they passed, so there must be a problem with the CI config. I tried to fix it with fc332eb with no success.

@TavoNiievez I've added two changes to help understand the error.

• Fail the test in case json decoding fails
• Temporary run codeception with -d to check what is the output on CI

@TavoNiievez can you remove my restriction to run CI tests at least for the duration of this PR?

@fkupper I'm not sure how to do that (or if possible). I think GitHub made that change because some people were taking advantage of builds to mine cryptocurrencies.

Have you tried activating Actions on your fork?

It seems that that was the problem, the last execution was correct, the only thing that generates a little doubt is knowing if disableMiddleware() deactivates all Middlewares, is there a way to specify that you only want to deactivate \App\Http\Middleware\VerifyCsrfToken ?

It seems that that was the problem, the last execution was correct, the only thing that generates a little doubt is knowing if disableMiddleware() deactivates all Middlewares, is there a way to specify that you only want to deactivate \App\Http\Middleware\VerifyCsrfToken ?

What do you think of using and api route instead of a web route? The api route group have no CSRF middleware.

What do you think of using and api route instead of a web route? The api route group have no CSRF middleware.

I've pushed the changes with this suggestion so you can have a look.

@fkupper good work!

thanks for your patience in this matter.

@fkupper good work!

thanks for your patience in this matter.

You're welcome!
My pleasure.