Skip to content
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

Closed
vworldat opened this issue Sep 26, 2017 · 18 comments
Closed

Integrate Codeception testing framework #45

vworldat opened this issue Sep 26, 2017 · 18 comments
Assignees
Milestone

Comments

@vworldat
Copy link

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?

@maks-rafalko
Copy link
Member

maks-rafalko commented Sep 26, 2017

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.

or have there been any blockers I don't know about yet

Several points to consider before implementation:

  1. We need to be able to pass such parameters as (they may have different names in Codeception)
    1.1 --stop-on-failure - to stop executing tests when the first is failed
    1.2 --configuration - to override location of configuration file

  2. Ideally we need to be able to generate junit.xml report. This is needed to fetch execution time of each test and sort them during mutation testing for performance reason

  3. And the most important thing: we need to be able to run only particular tests (e.g. test C, D) from the whole {A, B, C , D, E} testsuite. This is also for performance reason. But if it's impossible in Codeception, it does not block integration.


There are already two examples of integrated testing frameworks (PHPUnit, PhpSpec) so it's clear where to start.

@maks-rafalko maks-rafalko changed the title [Question] are there any plans to support codeception testing framework? Integrate Codeception testing framework Sep 28, 2017
@sidz
Copy link
Member

sidz commented Oct 16, 2017

@vworldat have you started to do anything?

@vworldat
Copy link
Author

@sidz not yet, unfortunately there was no time

@tobiasstadler
Copy link

Hi,
I integrated Codeception into Infection, see https://github.com/tobiasstadler/infection

I will create a PR once Codeception/Codeception#4562 (which is required by my implementation) is merged.

@vworldat
Copy link
Author

Wow, thanks a lot @tobiasstadler !

@DavertMik
Copy link

Merged at Codeception. The next release (2.3.8) will include those changes.

@metalcamp
Copy link

@DavertMik when is next release planned?

@DavertMik
Copy link

DavertMik commented Jan 11, 2018

Everything looks like is ready. I plan to make a release this month.
Meanwhile you can use 2.3.x-dev as dependency

@metalcamp
Copy link

@DavertMik: you mean dev-master or some other release?
I get following error when adding 2.3.x-dev to composer.json

Problem 1
    - The requested package infection/infection 2.3.x-dev exists as infection/infection[0.1.0, 0.2.0, 0.2.1, 0.3.0, 0.4.0, 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.6.0, 0.6.1, 0.6.2, 0.7.0, dev-master, dev-mockery10, dev-php-parser-400, dev-reflection, dev-reflection2, dev-theofidry-patch-1] but these are rejected by your constraint.

@maks-rafalko
Copy link
Member

maks-rafalko commented Jan 30, 2018

@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?

@sanmai
Copy link
Member

sanmai commented Mar 25, 2018

Codeception is at version 2.4.0 now FWIW.

@maks-rafalko
Copy link
Member

New WIP PR: #457

@voku
Copy link

voku commented Nov 6, 2018

any news on this?

@maks-rafalko
Copy link
Member

no news. AFAIK nobody works on it at the moment.

New PR is in #457

See #457 (comment)

@voku
Copy link

voku commented Nov 7, 2018

Thanks for the feedback, anyway.

@sanmai
Copy link
Member

sanmai commented Nov 7, 2018

See also #499 for general discussion.

@maks-rafalko
Copy link
Member

New PR and discussion will be here #800

@maks-rafalko
Copy link
Member

Implemented in #800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants