feat: adding devnet tests#12808
Merged
Merged
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
sklppy88
force-pushed
the
ek/feat/add-devnet-nightly-tests
branch
6 times, most recently
from
c2fe6d3 to
265b5d5
Compare
sklppy88
force-pushed
the
ek/feat/add-devnet-nightly-tests
branch
22 times, most recently
from
7477dc5 to
f5c2984
Compare
added 7 commits
April 9, 2025 02:34
nventuro
approved these changes
Apr 10, 2025
nventuro
left a comment
nventuro
left a comment
Contributor
There was a problem hiding this comment.
This reads much better, thank you for the effort in the splitting up and including appropriate descriptions, etc. Left some minor suggestions to include at your discretion. Let me know if you need help figuring out the errors you're encountering!
Using real values and rework SponsoredFPC env var fix ?
This reverts commit f536062.
Co-authored-by: Nicolás Venturo <nicolas.venturo@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am seeking advice / feedback on the methodology of the persistent tests.
This adds the first set of automated devnet tests.
The way this works is that at any specified time interval, we are creating x amount of accounts to a maximum of A (by bridging fee juice), creating y amount of token contracts to a maximum of B, and creating z amount of amm contracts to a maximum of C.
For each contract bundle we do some setup, and finally, for each account, we do a round robin set of public / private transfers, and for the AMM we add liquidity, swap, and remove liquidity.
Areas for improvment:
Spin up a unique wallet dir for each different "account"