Is there a kind of action in the EXPECT_CALL of Gmock?












0















The SUT is calling an external library for which an EXPECT_CALL is defined.
I want to only do something when the function is called for the first time and ignore doing anything the other time (but check that it's called twice); and vice versa.. i.e. do nothing the first time it is called and something the second time it is called.



// Code for the Expect Call  
EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
.WillOnce(do-nothing);

// SUT call
ASSERT_NO_THROW(sut_function(arg1, arg2));


Ignoring the second (do-nothing) WillOnce, I am getting a Gmock warning like:




GMOCK WARNING: test_blah-blah.cpp:321: Too few actions specified in
EXPECT_CALL(*mock_ptr, some-function(,))... Expected to be called
twice, but has only 1 WillOnce(). GMOCK WARNING:
test_blah-blah.cpp:321: Actions ran out in EXPECT_CALL(*mock_ptr,
some-function(,))... Called 2 times, but only 1 WillOnce() is
specified - returning directly.




What action do I give in the do-nothing part to not get this warning?
some-function is a void returning function.



Thanks!










share|improve this question





























    0















    The SUT is calling an external library for which an EXPECT_CALL is defined.
    I want to only do something when the function is called for the first time and ignore doing anything the other time (but check that it's called twice); and vice versa.. i.e. do nothing the first time it is called and something the second time it is called.



    // Code for the Expect Call  
    EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
    .WillOnce(do-nothing);

    // SUT call
    ASSERT_NO_THROW(sut_function(arg1, arg2));


    Ignoring the second (do-nothing) WillOnce, I am getting a Gmock warning like:




    GMOCK WARNING: test_blah-blah.cpp:321: Too few actions specified in
    EXPECT_CALL(*mock_ptr, some-function(,))... Expected to be called
    twice, but has only 1 WillOnce(). GMOCK WARNING:
    test_blah-blah.cpp:321: Actions ran out in EXPECT_CALL(*mock_ptr,
    some-function(,))... Called 2 times, but only 1 WillOnce() is
    specified - returning directly.




    What action do I give in the do-nothing part to not get this warning?
    some-function is a void returning function.



    Thanks!










    share|improve this question



























      0












      0








      0








      The SUT is calling an external library for which an EXPECT_CALL is defined.
      I want to only do something when the function is called for the first time and ignore doing anything the other time (but check that it's called twice); and vice versa.. i.e. do nothing the first time it is called and something the second time it is called.



      // Code for the Expect Call  
      EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
      .WillOnce(do-nothing);

      // SUT call
      ASSERT_NO_THROW(sut_function(arg1, arg2));


      Ignoring the second (do-nothing) WillOnce, I am getting a Gmock warning like:




      GMOCK WARNING: test_blah-blah.cpp:321: Too few actions specified in
      EXPECT_CALL(*mock_ptr, some-function(,))... Expected to be called
      twice, but has only 1 WillOnce(). GMOCK WARNING:
      test_blah-blah.cpp:321: Actions ran out in EXPECT_CALL(*mock_ptr,
      some-function(,))... Called 2 times, but only 1 WillOnce() is
      specified - returning directly.




      What action do I give in the do-nothing part to not get this warning?
      some-function is a void returning function.



      Thanks!










      share|improve this question
















      The SUT is calling an external library for which an EXPECT_CALL is defined.
      I want to only do something when the function is called for the first time and ignore doing anything the other time (but check that it's called twice); and vice versa.. i.e. do nothing the first time it is called and something the second time it is called.



      // Code for the Expect Call  
      EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
      .WillOnce(do-nothing);

      // SUT call
      ASSERT_NO_THROW(sut_function(arg1, arg2));


      Ignoring the second (do-nothing) WillOnce, I am getting a Gmock warning like:




      GMOCK WARNING: test_blah-blah.cpp:321: Too few actions specified in
      EXPECT_CALL(*mock_ptr, some-function(,))... Expected to be called
      twice, but has only 1 WillOnce(). GMOCK WARNING:
      test_blah-blah.cpp:321: Actions ran out in EXPECT_CALL(*mock_ptr,
      some-function(,))... Called 2 times, but only 1 WillOnce() is
      specified - returning directly.




      What action do I give in the do-nothing part to not get this warning?
      some-function is a void returning function.



      Thanks!







      unit-testing googletest googlemock






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 20 '18 at 16:30







      Sethuraman

















      asked Nov 20 '18 at 12:41









      SethuramanSethuraman

      53




      53
























          1 Answer
          1






          active

          oldest

          votes


















          0














          // Code for the Expect Call  
          EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
          .WillOnce(Return());

          // SUT call
          ASSERT_NO_THROW(sut_function(arg1, arg2));


          Adding Return() for the second(or the first) .WillOnce solved the problem. Referred to the cheatsheet in github to find the matching action.






          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%2f53393229%2fis-there-a-do-nothing-kind-of-action-in-the-expect-call-of-gmock%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            // Code for the Expect Call  
            EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
            .WillOnce(Return());

            // SUT call
            ASSERT_NO_THROW(sut_function(arg1, arg2));


            Adding Return() for the second(or the first) .WillOnce solved the problem. Referred to the cheatsheet in github to find the matching action.






            share|improve this answer




























              0














              // Code for the Expect Call  
              EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
              .WillOnce(Return());

              // SUT call
              ASSERT_NO_THROW(sut_function(arg1, arg2));


              Adding Return() for the second(or the first) .WillOnce solved the problem. Referred to the cheatsheet in github to find the matching action.






              share|improve this answer


























                0












                0








                0







                // Code for the Expect Call  
                EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
                .WillOnce(Return());

                // SUT call
                ASSERT_NO_THROW(sut_function(arg1, arg2));


                Adding Return() for the second(or the first) .WillOnce solved the problem. Referred to the cheatsheet in github to find the matching action.






                share|improve this answer













                // Code for the Expect Call  
                EXPECT_CALL(*mock_ptr, some-function(_,_)) .Times(2) .WillOnce(action1)
                .WillOnce(Return());

                // SUT call
                ASSERT_NO_THROW(sut_function(arg1, arg2));


                Adding Return() for the second(or the first) .WillOnce solved the problem. Referred to the cheatsheet in github to find the matching action.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 20 '18 at 16:35









                SethuramanSethuraman

                53




                53
































                    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%2f53393229%2fis-there-a-do-nothing-kind-of-action-in-the-expect-call-of-gmock%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

                    鏡平學校

                    ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

                    Why https connections are so slow when debugging (stepping over) in Java?