-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration test: Chainlink Pricer #120
Conversation
|
||
const ChainlinkPricer = artifacts.require('ChainLinkPricer.sol') | ||
const Oracle = artifacts.require('Oracle.sol') | ||
const MockChainlinkAggregator = artifacts.require('MockChainlinkAggregator.sol') |
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.
Can you use the actual chainLink contract instead of the mock
aggregator?
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.
I think using Mock make more sense in this case!
In tests we mock things that's out of our control. In this case, aggregator is not part of our system and we won't be able to directly write to the aggregator when we're live on mainnet, so I don't think that's should be included in the test.
Everything we care about is reading from the aggregator, and this is the perfect situation of using mock contracts. If we copy paste Chainlink aggregator, we will need like 10 steps to submit a price to the aggregator, and we can't do the same thing on Mainnet either
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.
LGTM.
closing because the change is covered in #126 |
Task: Feature Name:
High Level Description
Specific Changes
Function x was added ...
Code
Documentation