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?
node.js mocha smartcontracts web3 web3js
asked Nov 20 at 7:57
Vee6
5771224
add a comment |
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?
node.js mocha smartcontracts web3 web3js
asked Nov 20 at 7:57
Vee6
5771224
add a comment |
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?
node.js mocha smartcontracts web3 web3js
asked Nov 20 at 7:57
Vee6
5771224
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
node.js mocha smartcontracts web3 web3js
asked Nov 20 at 7:57
Vee6
5771224
asked Nov 20 at 7:57
Vee6
5771224
asked Nov 20 at 7:57
Vee6
5771224
asked Nov 20 at 7:57
Vee6
5771224
asked Nov 20 at 7:57
Vee6
5771224
5771224
add a comment |
add a comment |
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.
answered Nov 22 at 8:19
Vee6
5771224
add a comment |
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.
answered Nov 22 at 8:19
Vee6
5771224
add a comment |
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.
answered Nov 22 at 8:19
Vee6
5771224
add a comment |
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.
answered Nov 22 at 8:19
Vee6
5771224
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.
answered Nov 22 at 8:19
Vee6
5771224
answered Nov 22 at 8:19
Vee6
5771224
answered Nov 22 at 8:19
Vee6
5771224
answered Nov 22 at 8:19
Vee6
5771224
5771224
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
