You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.
When executing truffle test, it immediately invokes truffle deploy.
It is not really clear why truffle test is to be preceded by truffle deploy, since these two functionalities are essentially designated for two different goals.
Moreover, for Ganache users, it appears to be in contrast with the specification in the docs, which state:
Truffle provides a clean room environment when running your test files. When running your tests against Ganache or Truffle Develop, Truffle will use advanced snapshotting features to ensure your test files don't share state with each other. When running against other Ethereum clients like go-ethereum, Truffle will re-deploy all of your migrations at the beginning of every test file to ensure you have a fresh set of contracts to test against.
The implementation of this can be found in file /node_modules/truffle/build/cli.bundled.js:
Issue
When executing
truffle test
, it immediately invokestruffle deploy
.It is not really clear why
truffle test
is to be preceded bytruffle deploy
, since these two functionalities are essentially designated for two different goals.Moreover, for Ganache users, it appears to be in contrast with the specification in the docs, which state:
The implementation of this can be found in file
/node_modules/truffle/build/cli.bundled.js
:As you can see, function
run
first callsperformInitialDeploy
and then callssetJSTestGlobals
, which ultimately invokestests(accounts)
.Environment
The text was updated successfully, but these errors were encountered: