livepeer / livepeer/explorer

Consider adding anvil contract integration tests

Open
#558 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
11
Forks
26
Avg merge
11h 58m
Merged PRs (30d)
16

Description

### Is your feature request related to a problem?

- Currently there is no way for developers to test transaction flows before deployment without manually testing everything on a production chain
- The last testnet chains available in the explorer were goerli and rinkeby, but these are now deprecated

### Describe the solution you'd like

- We should add integration tests for all transaction flows using forked anvil contracts: https://www.getfoundry.sh/anvil#common-workflows
- These forked anvil contracts will simulate actual protocol contracts that exist on Arbitrum
- These tests should run in the CI, and be required to pass before any PRs are merged

### Describe alternatives you've considered

- Adding new Sepolia contracts were considered. However, forked anvil contracts should do the trick with even less work

### Additional context

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the transaction flows and existing CI configuration, then define coverage for all flows against forked Arbitrum contracts and require those tests to pass before merges.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, ci-cd, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.