{"id":2287,"date":"2019-01-11T08:23:57","date_gmt":"2019-01-10T19:23:57","guid":{"rendered":"http:\/\/www.talkcrypto.org\/blog\/?p=2287"},"modified":"2019-02-20T19:09:11","modified_gmt":"2019-02-20T06:09:11","slug":"where-is-deployedaddresses-sol-when-testing-in-truffle","status":"publish","type":"post","link":"https:\/\/www.talkcrypto.org\/blog\/2019\/01\/11\/where-is-deployedaddresses-sol-when-testing-in-truffle\/","title":{"rendered":"Where is DeployedAddresses.sol?"},"content":{"rendered":"

If you are creating test scripts in solidity, you may have come across these import statement:<\/p>\n

import \"truffle\/Assert.sol\";\nimport \"truffle\/DeployedAddresses.sol\";\nimport \"..\/contracts\/HelloWorld.sol\";<\/pre>\n
The last one is easy to understand because it is your smart contract in the “contracts” folder but what about Assert.sol and DeployedAddresses.sol?<\/p>\n
First of all, “truffle” refers to the global truffle repo which can be found at usr\/local\/lib\/node_modules\/truffle.<\/p>\n
Assert.sol lives at: usr\/local\/lib\/node_modules\/truffle\/build\/Assert.sol<\/p>\n
\"\"<\/a><\/p>\n
The trick is, what about DeployedAddresses.sol? You won’t find this file in the global truffle repo and a terminal search will be chocolateless<\/del> fruitless.<\/p>\n
\"\"<\/a><\/p>\n
The reason is because this file is dynamically created at test time. (Kindalike the geth.ipc file that gets generated when geth is running but disappears when geth is stopped).<\/p>\n
“truffle” is a meta package<\/a>, ie “these packages do not contain actual software, they simply depend on other packages to be installed<\/a>“. In fact, if you look at the deploy.js<\/a> source code, you’ll see the DeployedAddresses file get created via the code.<\/p>\n
\"\"<\/a><\/p>\n
Source:<\/p>\n