Skip to content

[Wallet] Move 7702 batch transaction test to integration tests #7166

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

Conversation

joaquim-verges
Copy link
Member

@joaquim-verges joaquim-verges commented May 27, 2025


PR-Codex overview

This PR refactors the integration tests for the inAppWallet, improving structure and adding new test cases for signing messages and sponsoring gas for smart accounts.

Detailed summary

  • Replaced describe with describe.runIf(process.env.TW_SECRET_KEY) for conditional test execution.
  • Added new tests for signing messages with both "backend" and "guest" strategies.
  • Updated test for sponsoring gas for a 7702 smart account.
  • Introduced a test for batch transactions for a 7702 account.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • Tests
    • Improved organization of in-app wallet integration tests by running them conditionally based on environment setup.
    • Added a new test for batching multiple transactions with 7702 accounts on the Base Sepolia network.
    • Enhanced event log validation for EIP-4337 smart account tests.
    • Removed a separate minimal account test suite, consolidating relevant tests into the main integration suite.

Copy link

changeset-bot bot commented May 27, 2025

⚠️ No Changeset found

Latest commit: f280ca5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented May 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2025 2:32am
login ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2025 2:32am
thirdweb_playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2025 2:32am
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2025 2:32am
wallet-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2025 2:32am

Copy link
Contributor

coderabbitai bot commented May 27, 2025

Walkthrough

The changes involve reorganizing and consolidating tests for in-app wallet functionality. A test file for EIP-7702 minimal account batch transactions was deleted, and its core batch transaction test was integrated into the main in-app wallet integration test suite. All integration tests now run conditionally based on an environment variable.

Changes

File(s) Change Summary
.../core/eip7702/minimal-account.test.ts Deleted test file for EIP-7702 minimal account batch transactions.
.../web/lib/in-app-integration.test.ts Refactored tests to run conditionally on TW_SECRET_KEY, integrated batch transaction test, updated imports.

Sequence Diagram(s)

sequenceDiagram
    participant TestSuite
    participant InAppWallet
    participant BlockchainClient
    participant Chain
    participant Account

    TestSuite->>InAppWallet: Instantiate (EIP-7702, gas sponsorship)
    InAppWallet->>BlockchainClient: Connect (guest strategy, baseSepolia)
    TestSuite->>Account: Generate addresses (2x)
    TestSuite->>InAppWallet: Prepare batch transactions (to Account1, Account2)
    InAppWallet->>BlockchainClient: Send batch transaction
    BlockchainClient-->>InAppWallet: Return transaction hash
    InAppWallet-->>TestSuite: Assert transaction hash is defined
Loading

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@joaquim-verges joaquim-verges marked this pull request as ready for review May 27, 2025 02:22
@joaquim-verges joaquim-verges requested review from a team as code owners May 27, 2025 02:22
@github-actions github-actions bot added packages SDK Involves changes to the thirdweb SDK labels May 27, 2025
Copy link
Member Author


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/thirdweb/src/wallets/in-app/web/lib/in-app-integration.test.ts (1)

119-149: Consider adding event log validation to the batch transaction test.

The batch transaction test is functionally correct but lacks the comprehensive validation present in other tests. Consider adding event log parsing to verify that both transactions in the batch were executed successfully.

Add event log validation similar to the other tests:

  const result = await sendBatchTransaction({
    account,
    transactions: [tx1, tx2],
  });
  expect(result.transactionHash).toBeDefined();
+ const logs = parseEventLogs({
+   logs: result.logs,
+   events: [executedEvent()],
+ });
+ expect(logs).toHaveLength(2); // Verify both transactions were executed
+ logs.forEach((log) => {
+   expect(log.args.value).toBe(0n);
+ });
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 80207ae and f280ca5.

📒 Files selected for processing (2)
  • packages/thirdweb/src/wallets/in-app/core/eip7702/minimal-account.test.ts (0 hunks)
  • packages/thirdweb/src/wallets/in-app/web/lib/in-app-integration.test.ts (1 hunks)
💤 Files with no reviewable changes (1)
  • packages/thirdweb/src/wallets/in-app/core/eip7702/minimal-account.test.ts
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Unit Tests
  • GitHub Check: Build Packages
  • GitHub Check: Size
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (5)
packages/thirdweb/src/wallets/in-app/web/lib/in-app-integration.test.ts (5)

3-3: LGTM! Appropriate imports for new functionality.

The new imports (baseSepolia, sendBatchTransaction, generateAccount) are correctly added to support the new batch transaction test functionality.

Also applies to: 9-9, 11-11


14-16: Excellent use of conditional test execution.

Using describe.runIf(process.env.TW_SECRET_KEY) is a best practice for integration tests that require credentials, preventing test failures in environments where the secret key is not available.


17-29: Message signing tests look good.

Both backend and guest strategy tests are properly structured and verify the expected functionality. The tests correctly assert that both the account address and signed message are defined.

Also applies to: 31-42


44-78: Well-implemented EIP-7702 gas sponsorship test.

The test properly verifies gas sponsorship functionality and includes comprehensive event log validation to ensure the transaction was executed correctly with the expected parameters.


80-117: Enhanced EIP-4337 test with proper event validation.

The test correctly validates userOperationEventEvent logs and checks both sender address and success status, providing good coverage for the EIP-4337 execution mode.

Copy link

codecov bot commented May 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.66%. Comparing base (80207ae) to head (f280ca5).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7166   +/-   ##
=======================================
  Coverage   55.66%   55.66%           
=======================================
  Files         904      904           
  Lines       58391    58391           
  Branches     4111     4112    +1     
=======================================
  Hits        32505    32505           
+ Misses      25781    25780    -1     
- Partials      105      106    +1     
Flag Coverage Δ
packages 55.66% <ø> (ø)

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 61.75 KB (0%) 1.3 s (0%) 384 ms (+133.01% 🔺) 1.7 s
thirdweb (cjs) 344.4 KB (0%) 6.9 s (0%) 1.3 s (-1.55% 🔽) 8.2 s
thirdweb (minimal + tree-shaking) 5.69 KB (0%) 114 ms (0%) 123 ms (+1095.2% 🔺) 237 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 33 ms (+607.17% 🔺) 44 ms
thirdweb/react (minimal + tree-shaking) 19.54 KB (0%) 391 ms (0%) 213 ms (+759.16% 🔺) 603 ms

@joaquim-verges joaquim-verges merged commit aec8d88 into main May 27, 2025
27 checks passed
@joaquim-verges joaquim-verges deleted the _Wallet_Move_7702_batch_transaction_test_to_integration_tests branch May 27, 2025 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
packages SDK Involves changes to the thirdweb SDK
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant