You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are relying somewhat on monorepo tests such as the kurtosis, NAT and op-e2e tests for asserting the correctness of op-geth behaviors. It would be good to encode this reliance more explicitly by having the CI within op-geth run these tests in repo pull requests.
If we can write tests more simply by writing them using high-level test frameworks like those exposed by kurtosis and NAT, and also depend on these tests to be consulted before merging any code to the op-geth repo, then we can increase confidence in changes to the repo and increase test coverage by ensuring clean CI integration.
Implementation
Do you have ideas regarding the implementation of this feature?
TODO
Are you willing to implement this feature?
Yes, although it may be a better fit for the platform team.
The text was updated successfully, but these errors were encountered:
Rationale
Right now we are relying somewhat on monorepo tests such as the kurtosis, NAT and op-e2e tests for asserting the correctness of op-geth behaviors. It would be good to encode this reliance more explicitly by having the CI within op-geth run these tests in repo pull requests.
If we can write tests more simply by writing them using high-level test frameworks like those exposed by kurtosis and NAT, and also depend on these tests to be consulted before merging any code to the op-geth repo, then we can increase confidence in changes to the repo and increase test coverage by ensuring clean CI integration.
Implementation
Do you have ideas regarding the implementation of this feature?
TODO
Are you willing to implement this feature?
Yes, although it may be a better fit for the platform team.
The text was updated successfully, but these errors were encountered: