Conversation
Refactored gasLimit, gasPrices, gas, custom_gas_limit, custom_gas_price.
Updated bootstrap and compileAndDeploy module
Added getWeb3 Added preloadWeb3 (get web3 with mocha support)
So many of these tests are validating that an option was properly handled/observed. Given that this is mostly following a pattern of "set option to nondefault value then validate that the option was set", I wonder if this couldn't/shouldn't be handled by a test helper. That way we could have a single "it observes gas options" test which just runs through a list of options |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a high level this looks like a step in the right direction, but I'm a bit confused by some things (see inline comments).
As mentioned in Slack, please don't delete this PR, just submit changes to the same branch so we can preserve the comment history.
Added toHex to `helpers/utils` Ignoring .nyc_output Update references to toBytesHexString
Extracting the options to a helper file would be ideal and a great start to increasing coverage stats. We can target this during the next refactoring pass through. |
…flesuite/ganache-core into refactored-gas-test-history
Ben has better things to do right now. :-D
Added missing documentation to bootstrap module
Refactored and grouped gas related tests
Fixed reference errors to old helper files
Fixed a couple of module export definitions