Skip to content
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

[Tracking] Setup integration tests #15

Closed
3 tasks done
alexfertel opened this issue Mar 25, 2024 · 2 comments
Closed
3 tasks done

[Tracking] Setup integration tests #15

alexfertel opened this issue Mar 25, 2024 · 2 comments
Assignees
Labels
effort: high Large or difficult task. type: test Changes to the testing suite. uphill Some research/design is needed before this can be implemented.

Comments

@alexfertel
Copy link
Contributor

alexfertel commented Mar 25, 2024

This issue tracks the work required to set up the infrastructure for our integration test suite.

This work is mainly blocked because we need a reliable, fast way of booting up a local, Stylus-compatible fork. Ideally, we have something like anvil, provided by the Stylus team.

  • Spike: Create a PoC with anvil that showcases the missing pieces required to make it work with Stylus.
  • Spike: Research possible alternatives.

Tasks

Preview Give feedback
  1. effort: medium priority: 3 type: test
    qalisander
  2. needs triage type: feature
    qalisander
  3. effort: medium priority: 2 type: refactor
    alexfertel
@alexfertel alexfertel converted this from a draft issue Mar 25, 2024
@alexfertel alexfertel added priority: 2 type: test Changes to the testing suite. effort: high Large or difficult task. uphill Some research/design is needed before this can be implemented. and removed priority: 2 labels Mar 25, 2024
@alexfertel alexfertel added this to the Release v0.1.0 milestone Mar 25, 2024
@alexfertel alexfertel self-assigned this Apr 3, 2024
@alexfertel
Copy link
Contributor Author

After some time researching this, we concluded that it's not possible without the help of the Stylus team.

Until they have the capacity to help us with this, we will take the approach of booting up nitro-testnode locally and running our tests against it. This will be based on previous work by myself and @qalisander

@alexfertel
Copy link
Contributor Author

Completed!

@github-project-automation github-project-automation bot moved this from Blocked to Done in Rust Contracts Stylus Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: high Large or difficult task. type: test Changes to the testing suite. uphill Some research/design is needed before this can be implemented.
Projects
Status: Done
Development

No branches or pull requests

2 participants