Blockchain
CBDE
Q1:
Integrating the community into your testing:
○
A
is great, because they often find bugs which weren't considered before.○
B
is not good, because you might give out secrets.
Blockchain
CBDE
Q2:
Truffle boxes are a great way:
○
A
to contribute to the box community which is the distributed file system for truffle.○
B
to start with a pre-configured environment for most web-development needs.○
C
to use tools that makes boxing of Dapps for different platforms very easy.
Blockchain
CBDE
Q3:
With the truffle config file you can manage:
○
A
the amount of gas your contract deployment and transactions, against your contract, will need. This way you can essentially lower the gas costs over traditional web3.js dApps.○
B
different Networks to deploy your contracts to. This way you can easily deploy to a local blockchain, the main-net or the Ropsten/Rinkeby Test-Net with only one parameter.○
C
you can manage your secret API keys to the Ethereum Network. This way you can get access to several different Ethereum nodes at the same time without the need to switch your keyfiles.
Blockchain
CBDE
Q4:
It's easy to write clean-room unit-tests with truffle:
○
A
for Java, JavaScript, and C++○
B
for JavaScript using Web3.js○
C
for Solidity and JavaScript○
D
for any language, as long as it adheres to the open Testing-Interface from Truffle
Blockchain
CBDE
Q5:
Unit-Testing on a local chain is important, because it helps you:
○
A
to run tests quickly and especially for free, compared to continuous deployment on the MainNetwork. This way you save a lot of fees, time and costs.○
B
to run tests in an environment where logging is activated. On the Main-Net you have no access to transaction logs and this is ultimately the information you need to debug your contracts.○
C
to avoid regression bugs with contracts that are updated constantly on the main-net. Once you update a contract on the main-net, the address stays the same, but the code changes and this can have disastrous side-effects.