Mocha tests hang after completion when working with web3 smart contracts











up vote
0
down vote

favorite












I wrote some integration tests for a node app that works with Ethereum smart contracts (and thus use the contracts' state as a data storage). I am instantiating some smart contracts interfaces using web3 and in the assertion parts of the tests I am using them to check that valid information has been written to the blockchain.



However after the tests pass the mocha process is still running and I have to shut it down manually. I suspect this happens because the smart contract interfaces are basically open connections and they are not closed, I know it happens when you do the same with normal database connections (see here: Mocha hangs after execution when connecting with Mongoose).



I didn't find any disconnect or similar web3 api methods though, anyone had any similar experience with this?










share|improve this question


























    up vote
    0
    down vote

    favorite












    I wrote some integration tests for a node app that works with Ethereum smart contracts (and thus use the contracts' state as a data storage). I am instantiating some smart contracts interfaces using web3 and in the assertion parts of the tests I am using them to check that valid information has been written to the blockchain.



    However after the tests pass the mocha process is still running and I have to shut it down manually. I suspect this happens because the smart contract interfaces are basically open connections and they are not closed, I know it happens when you do the same with normal database connections (see here: Mocha hangs after execution when connecting with Mongoose).



    I didn't find any disconnect or similar web3 api methods though, anyone had any similar experience with this?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I wrote some integration tests for a node app that works with Ethereum smart contracts (and thus use the contracts' state as a data storage). I am instantiating some smart contracts interfaces using web3 and in the assertion parts of the tests I am using them to check that valid information has been written to the blockchain.



      However after the tests pass the mocha process is still running and I have to shut it down manually. I suspect this happens because the smart contract interfaces are basically open connections and they are not closed, I know it happens when you do the same with normal database connections (see here: Mocha hangs after execution when connecting with Mongoose).



      I didn't find any disconnect or similar web3 api methods though, anyone had any similar experience with this?










      share|improve this question













      I wrote some integration tests for a node app that works with Ethereum smart contracts (and thus use the contracts' state as a data storage). I am instantiating some smart contracts interfaces using web3 and in the assertion parts of the tests I am using them to check that valid information has been written to the blockchain.



      However after the tests pass the mocha process is still running and I have to shut it down manually. I suspect this happens because the smart contract interfaces are basically open connections and they are not closed, I know it happens when you do the same with normal database connections (see here: Mocha hangs after execution when connecting with Mongoose).



      I didn't find any disconnect or similar web3 api methods though, anyone had any similar experience with this?







      node.js mocha smartcontracts web3 web3js






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 at 7:57









      Vee6

      5771224




      5771224
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Someone pointed me that there is an --exit flag that you can pass to mocha and it kills the process after all tests have finished running, probably a good enough solution for now.






          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',
            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%2f53388528%2fmocha-tests-hang-after-completion-when-working-with-web3-smart-contracts%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








            up vote
            0
            down vote













            Someone pointed me that there is an --exit flag that you can pass to mocha and it kills the process after all tests have finished running, probably a good enough solution for now.






            share|improve this answer

























              up vote
              0
              down vote













              Someone pointed me that there is an --exit flag that you can pass to mocha and it kills the process after all tests have finished running, probably a good enough solution for now.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                Someone pointed me that there is an --exit flag that you can pass to mocha and it kills the process after all tests have finished running, probably a good enough solution for now.






                share|improve this answer












                Someone pointed me that there is an --exit flag that you can pass to mocha and it kills the process after all tests have finished running, probably a good enough solution for now.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 8:19









                Vee6

                5771224




                5771224






























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f53388528%2fmocha-tests-hang-after-completion-when-working-with-web3-smart-contracts%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

                    To store a contact into the json file from server.js file using a class in NodeJS

                    Redirect URL with Chrome Remote Debugging Android Devices

                    Dieringhausen