How can i improve Codeception Code Coverage speedHow can I prevent SQL injection in PHP?What is a reasonable code coverage % for unit tests (and why)?What can I use for good quality code coverage for C#/.NET?Reaching 100% Code Coverage with PHPUnitCodeigniter 2 and codeceptionCode coverage with MochaHow to trouble shoot codeception unit tests in laravel 4Speeding up PHPUnit startup when code coverage is not requiredCodeception code coverage lowcode coverage report not correct after upgrading to PHPUnit 5.5.4

Are athletes' college degrees discounted by employers and graduate school admissions?

Would a bit of grease on overhead door cables or bearings cause the springs to break?

Print the phrase "And she said, 'But that's his.'" using only the alphabet

Purpose of cylindrical attachments on Power Transmission towers

Someone who is granted access to information but not expected to read it

Harley Davidson clattering noise from engine, backfire and failure to start

I received a gift from my sister who just got back from

What is the theme of analysis?

Jam with honey & without pectin has a saucy consistency always

Interview was just a one hour panel. Got an offer the next day; do I accept or is this a red flag?

Can Mage Hand be used to indirectly trigger an attack?

The best in flight meal option for those suffering from reflux

Any gotchas in buying second-hand sanitary ware?

Optimising matrix generation time

SFDX force:org:clone not working

Can artificial satellite positions affect tides?

Difference between grep -R and -r

How can this shape perfectly cover a cube?

Short story about psychologist analyzing demon

If statement with arcpy

Can a 40amp breaker be used safely and without issue with a 40amp device on 6AWG wire?

Can I get a photo of an Ancient Arrow?

My players want to use called-shots on Strahd

Can an escape pod land on Earth from orbit and not be immediately detected?



How can i improve Codeception Code Coverage speed


How can I prevent SQL injection in PHP?What is a reasonable code coverage % for unit tests (and why)?What can I use for good quality code coverage for C#/.NET?Reaching 100% Code Coverage with PHPUnitCodeigniter 2 and codeceptionCode coverage with MochaHow to trouble shoot codeception unit tests in laravel 4Speeding up PHPUnit startup when code coverage is not requiredCodeception code coverage lowcode coverage report not correct after upgrading to PHPUnit 5.5.4






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















Currently we have written some unit test for our php laravel 5.5 application using codeception. just for additional info, our laravel code base have around 200k LOC. For normal unit test run, we noticed that it is really fast in which we can get more than 200 tests to finish within 1 hour.



But the main issue is that when we enabled codecoverage in codeception which is using xdebug by default, we noticed the execution time increased drastically.



Now it already took 1 week but the whole codecoverage execution not even finished yet.



I am not sure whether this is the problem from codeception or xdebug itself but if anybody have experiences running php codecoverage on a huge codebase, it would be nice if you can share how you achieve it. Would appreciate it also if somebody can suggest any other tools to look into. Currently we are considering switching to phpunit but are still open to other tools to explore.










share|improve this question




























    0















    Currently we have written some unit test for our php laravel 5.5 application using codeception. just for additional info, our laravel code base have around 200k LOC. For normal unit test run, we noticed that it is really fast in which we can get more than 200 tests to finish within 1 hour.



    But the main issue is that when we enabled codecoverage in codeception which is using xdebug by default, we noticed the execution time increased drastically.



    Now it already took 1 week but the whole codecoverage execution not even finished yet.



    I am not sure whether this is the problem from codeception or xdebug itself but if anybody have experiences running php codecoverage on a huge codebase, it would be nice if you can share how you achieve it. Would appreciate it also if somebody can suggest any other tools to look into. Currently we are considering switching to phpunit but are still open to other tools to explore.










    share|improve this question
























      0












      0








      0








      Currently we have written some unit test for our php laravel 5.5 application using codeception. just for additional info, our laravel code base have around 200k LOC. For normal unit test run, we noticed that it is really fast in which we can get more than 200 tests to finish within 1 hour.



      But the main issue is that when we enabled codecoverage in codeception which is using xdebug by default, we noticed the execution time increased drastically.



      Now it already took 1 week but the whole codecoverage execution not even finished yet.



      I am not sure whether this is the problem from codeception or xdebug itself but if anybody have experiences running php codecoverage on a huge codebase, it would be nice if you can share how you achieve it. Would appreciate it also if somebody can suggest any other tools to look into. Currently we are considering switching to phpunit but are still open to other tools to explore.










      share|improve this question














      Currently we have written some unit test for our php laravel 5.5 application using codeception. just for additional info, our laravel code base have around 200k LOC. For normal unit test run, we noticed that it is really fast in which we can get more than 200 tests to finish within 1 hour.



      But the main issue is that when we enabled codecoverage in codeception which is using xdebug by default, we noticed the execution time increased drastically.



      Now it already took 1 week but the whole codecoverage execution not even finished yet.



      I am not sure whether this is the problem from codeception or xdebug itself but if anybody have experiences running php codecoverage on a huge codebase, it would be nice if you can share how you achieve it. Would appreciate it also if somebody can suggest any other tools to look into. Currently we are considering switching to phpunit but are still open to other tools to explore.







      php unit-testing code-coverage laravel-5.5 codeception






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 25 at 1:19









      AlamHoAlamHo

      3417




      3417






















          2 Answers
          2






          active

          oldest

          votes


















          2














          Replacing Codeception with PHPUnit will be a lot of work for little gain, because Codeception uses PHPUnit and its PHP-Code-Coverage library under the hood.



          There is a new code coverage extension, called pcov which is supposedly much faster than xdebug.
          https://github.com/krakjoe/pcov/blob/develop/INSTALL.md



          I haven't tried to use it, but be aware that it requires PHPUnit 8, which is only available on PHP 7.2 or later versions.






          share|improve this answer























          • Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

            – AlamHo
            Mar 26 at 0:34






          • 1





            You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

            – Joe Watkins
            Mar 26 at 19:00


















          0














          Recently I have seen code coverage sped up by replacing xdebug with phpdbg - I can't give exact numbers as the code base has extensive functional tests in its test run (and the speed-up was only for unit tests), but a 2+ hour test and coverage run has been reduced to around 50 minutes.



          Note that xdebug and phpdbg can differ in their code coverage (it looked like xdebug better dealt with opcache optimisations).






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55330191%2fhow-can-i-improve-codeception-code-coverage-speed%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Replacing Codeception with PHPUnit will be a lot of work for little gain, because Codeception uses PHPUnit and its PHP-Code-Coverage library under the hood.



            There is a new code coverage extension, called pcov which is supposedly much faster than xdebug.
            https://github.com/krakjoe/pcov/blob/develop/INSTALL.md



            I haven't tried to use it, but be aware that it requires PHPUnit 8, which is only available on PHP 7.2 or later versions.






            share|improve this answer























            • Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

              – AlamHo
              Mar 26 at 0:34






            • 1





              You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

              – Joe Watkins
              Mar 26 at 19:00















            2














            Replacing Codeception with PHPUnit will be a lot of work for little gain, because Codeception uses PHPUnit and its PHP-Code-Coverage library under the hood.



            There is a new code coverage extension, called pcov which is supposedly much faster than xdebug.
            https://github.com/krakjoe/pcov/blob/develop/INSTALL.md



            I haven't tried to use it, but be aware that it requires PHPUnit 8, which is only available on PHP 7.2 or later versions.






            share|improve this answer























            • Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

              – AlamHo
              Mar 26 at 0:34






            • 1





              You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

              – Joe Watkins
              Mar 26 at 19:00













            2












            2








            2







            Replacing Codeception with PHPUnit will be a lot of work for little gain, because Codeception uses PHPUnit and its PHP-Code-Coverage library under the hood.



            There is a new code coverage extension, called pcov which is supposedly much faster than xdebug.
            https://github.com/krakjoe/pcov/blob/develop/INSTALL.md



            I haven't tried to use it, but be aware that it requires PHPUnit 8, which is only available on PHP 7.2 or later versions.






            share|improve this answer













            Replacing Codeception with PHPUnit will be a lot of work for little gain, because Codeception uses PHPUnit and its PHP-Code-Coverage library under the hood.



            There is a new code coverage extension, called pcov which is supposedly much faster than xdebug.
            https://github.com/krakjoe/pcov/blob/develop/INSTALL.md



            I haven't tried to use it, but be aware that it requires PHPUnit 8, which is only available on PHP 7.2 or later versions.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 25 at 8:48









            NaktibaldaNaktibalda

            10.1k32443




            10.1k32443












            • Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

              – AlamHo
              Mar 26 at 0:34






            • 1





              You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

              – Joe Watkins
              Mar 26 at 19:00

















            • Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

              – AlamHo
              Mar 26 at 0:34






            • 1





              You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

              – Joe Watkins
              Mar 26 at 19:00
















            Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

            – AlamHo
            Mar 26 at 0:34





            Does that mean that on php currently there are no known code coverage tool that can be run on a huge codebase? Another idea that we had was to break the monolithic apps into microservices but that would require major rewrite of the entire application. Thanks for the reply anyway

            – AlamHo
            Mar 26 at 0:34




            1




            1





            You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

            – Joe Watkins
            Mar 26 at 19:00





            You can use pcov on whatever size codebase you like ... you may also use pcov on versions of PHPUnit before 8 (tested down to 6.5), with some hackery ... hackery contained in github.com/krakjoe/pcov-clobber ... my advice (I wrote pcov) would be to update to PHPUnit 8, as soon as possible ...

            – Joe Watkins
            Mar 26 at 19:00













            0














            Recently I have seen code coverage sped up by replacing xdebug with phpdbg - I can't give exact numbers as the code base has extensive functional tests in its test run (and the speed-up was only for unit tests), but a 2+ hour test and coverage run has been reduced to around 50 minutes.



            Note that xdebug and phpdbg can differ in their code coverage (it looked like xdebug better dealt with opcache optimisations).






            share|improve this answer



























              0














              Recently I have seen code coverage sped up by replacing xdebug with phpdbg - I can't give exact numbers as the code base has extensive functional tests in its test run (and the speed-up was only for unit tests), but a 2+ hour test and coverage run has been reduced to around 50 minutes.



              Note that xdebug and phpdbg can differ in their code coverage (it looked like xdebug better dealt with opcache optimisations).






              share|improve this answer

























                0












                0








                0







                Recently I have seen code coverage sped up by replacing xdebug with phpdbg - I can't give exact numbers as the code base has extensive functional tests in its test run (and the speed-up was only for unit tests), but a 2+ hour test and coverage run has been reduced to around 50 minutes.



                Note that xdebug and phpdbg can differ in their code coverage (it looked like xdebug better dealt with opcache optimisations).






                share|improve this answer













                Recently I have seen code coverage sped up by replacing xdebug with phpdbg - I can't give exact numbers as the code base has extensive functional tests in its test run (and the speed-up was only for unit tests), but a 2+ hour test and coverage run has been reduced to around 50 minutes.



                Note that xdebug and phpdbg can differ in their code coverage (it looked like xdebug better dealt with opcache optimisations).







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 24 at 4:58









                tschumanntschumann

                13418




                13418



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55330191%2fhow-can-i-improve-codeception-code-coverage-speed%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

                    SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

                    은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현