-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Ks 323 keystone evm integration tests #13838
Conversation
99a8152
to
66d56d1
Compare
a90a763
to
6cd2701
Compare
e83b4a2
to
de65458
Compare
"github.com/smartcontractkit/chainlink-common/pkg/values" | ||
) | ||
|
||
const triggerID = "streams-trigger@1.0.0" |
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 actually have a similar thing here, I'm hoping we could just make this a new trigger type useful for testing/development in the core node: https://github.com/smartcontractkit/chainlink/pull/13716/files#diff-905de3fd1acdb9e2daa319880d9a528cca7f034d3b8920eec76905b7e6b52acd
3c5e80a
to
281a960
Compare
31d1fed
to
56737e0
Compare
1eebd5f
to
3f80c08
Compare
e416ca6
to
f6199c8
Compare
e81299f
to
c24852c
Compare
Quality Gate passedIssues Measures |
https://smartcontract-it.atlassian.net/browse/KS-323
Framework for running end to end tests for keystone. The test framework utilizes all keystone contracts and simulates running a trigger DON, workflow DON and target DON. It achieves this by mocking out the dispatcher and libocr to simulate a multi DON environment within the testing process. It uses the existing integration testing framework to instantiate nodes and uses the geth simulated backed to run all required contract code.
A couple of tests are implemented as part of this PR to test the framework and serve as examples. TBD Each tests takes in the region of 5s to run, possible this could also be improved by decreasing the block time and ocr protocol round time.