New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Codeception testing framework #45
Comments
Hello, thank you for posting this question. I'm not aware of any activity about integrating Infection with Codeception. Wouldn't you want to be the first one? :) As soon as it supports code coverage (just checked - it supports), I think there is no problem to do it.
Several points to consider before implementation:
There are already two examples of integrated testing frameworks (PHPUnit, PhpSpec) so it's clear where to start. |
@vworldat have you started to do anything? |
@sidz not yet, unfortunately there was no time |
Hi, I will create a PR once Codeception/Codeception#4562 (which is required by my implementation) is merged. |
Wow, thanks a lot @tobiasstadler ! |
Merged at Codeception. The next release (2.3.8) will include those changes. |
@DavertMik when is next release planned? |
Everything looks like is ready. I plan to make a release this month. |
@DavertMik: you mean dev-master or some other release?
|
@metalcamp current Infection version is 0.7.0. @DavertMik was writing about 2.3.8 version of Codeception. Codeception is not supported by Infection at the moment. @tobiasstadler any news on your branch? |
Codeception is at version 2.4.0 now FWIW. |
New WIP PR: #457 |
any news on this? |
no news. AFAIK nobody works on it at the moment. New PR is in #457 See #457 (comment) |
Thanks for the feedback, anyway. |
See also #499 for general discussion. |
New PR and discussion will be here #800 |
Implemented in #800 |
I'm using codeception as my main testing framework and may be interested in providing the integration. Has anybody else already started working on codeception integration or have there been any blockers I don't know about yet?
The text was updated successfully, but these errors were encountered: