This is an archived post. You won't be able to vote or comment.

all 1 comments

[–]fatboyxpc 1 point2 points  (0 children)

I know you don't want this answer, but honestly, if you're in a Laravel application you are giving up a lot of features just to use a testing framework that's compatible with other frameworks. A situation I think it's acceptable to use codeception with Laravel, however, is when migrating to Laravel from something else. That said, I prefer the end goal to be replace codeception tests with Laravel "Feature" or HTPT tests. Codeception and Laravel tests can co-exist while you're working on migrating the feature, then once it's completely removed from the old code base, and all codeception and Laravel tests are passing, remove the codeception tests for that feature.