test: add multi-transaction ERC20 integration test#1590
test: add multi-transaction ERC20 integration test#1590giwaov wants to merge 1 commit intogenlayerlabs:mainfrom
Conversation
Adds a new integration test that deploys a single LlmErc20 contract and runs multiple sequential transactions against it with three accounts: - A -> B transfer - A -> C transfer - B -> C transfer (using connect() to switch sender) After each transaction, balances are verified. A final assertion checks that total supply is preserved across all transfers. This tests the scenario described in genlayerlabs#441: running multiple transactions against the same contract to expose potential race conditions or state corruption between consecutive writes. Closes genlayerlabs#441
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 11 minutes and 28 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Adds a new integration test that deploys a single \LlmErc20\ contract and runs multiple sequential transactions against it, verifying balances and total supply preservation after each transfer.
Changes
Test Scenario
This catches potential race conditions or state corruption when multiple writes hit the same contract sequentially, as described in issue #441.
Labels
This issue is tagged \good first issue.
Related Issue
Closes #441