-
Notifications
You must be signed in to change notification settings - Fork 304
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
cw/fix tests e2e staging #1590
cw/fix tests e2e staging #1590
Conversation
d743dda
to
dc602b6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1590 +/- ##
=====================================
Coverage 63.6% 63.7%
=====================================
Files 44 44
Lines 8337 8337
=====================================
+ Hits 5304 5311 +7
+ Misses 3033 3026 -7 ☔ View full report in Codecov by Sentry. |
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.
is the way one runs e2e tests affected? should we add something in the readme about deploying a relayer fleet with a specific private key in env?
5ab4027
to
18d072b
Compare
85ea0d2
to
3f8f9b1
Compare
9386e05
to
3ac8b41
Compare
4b25622
to
50d3802
Compare
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.
end-to-end tests could be pulling the state from SN Sepolia when starting Katana so that we run everything like on a sepolia deployment?
This change is